From 5d608c1e2aebddbb6f9c65507f5f6ef99632df15 Mon Sep 17 00:00:00 2001 From: Vanessa Yuen <6842965+vanessayuenn@users.noreply.github.com> Date: Tue, 9 Feb 2021 18:14:25 +0100 Subject: [PATCH] Crowdin translations (translation-batch-1612885307) (#17760) * New Crowdin translations by Github Action * Revert broken translated files to content from branch * fix known frontmatter errors * Revert broken translated files to content from branch * fix translation errors Co-authored-by: Crowdin Bot Co-authored-by: Jason Etcovitch --- .../about-self-hosted-runners.md | 10 +- ...using-self-hosted-runners-in-a-workflow.md | 2 +- ...pecifications-for-github-hosted-runners.md | 77 +++++---- ...guring-code-scanning-for-your-appliance.md | 2 +- ...ing-data-encryption-for-your-enterprise.md | 14 +- .../upgrading-github-enterprise-server.md | 20 +++ ...ub-actions-for-github-enterprise-server.md | 34 +++- ...orking-repositories-from-github-desktop.md | 44 ++--- .../managing-tags.md | 6 +- .../apps/activating-beta-features-for-apps.md | 2 + .../apps/authenticating-with-github-apps.md | 2 +- .../creating-ci-tests-with-the-checks-api.md | 6 +- .../migrating-oauth-apps-to-github-apps.md | 4 +- ...refreshing-user-to-server-access-tokens.md | 2 +- .../suspending-a-github-app-installation.md | 2 + .../handling-new-purchases-and-free-trials.md | 18 +- ...bout-using-replit-with-github-classroom.md | 2 +- .../about-dependabot-version-updates.md | 5 +- .../about-protected-branches.md | 12 +- .../about-securing-your-repository.md | 18 +- ...g-secret-scanning-for-your-repositories.md | 6 +- ...ge-for-pull-requests-in-your-repository.md | 5 +- ...d-analysis-settings-for-your-repository.md | 11 +- .../securing-your-repository.md | 1 + .../setting-repository-visibility.md | 2 +- .../associating-an-email-with-your-gpg-key.md | 10 +- .../automatically-merging-a-pull-request.md | 3 +- .../merging-a-pull-request.md | 1 - .../about-code-owners.md | 2 +- .../about-code-scanning.md | 23 +-- ...-codeql-code-scanning-in-your-ci-system.md | 29 ++-- ...-codeql-workflow-for-compiled-languages.md | 2 +- .../index.md | 2 +- ...ode-scanning-alerts-for-your-repository.md | 8 +- ...-codeql-code-scanning-in-your-ci-system.md | 2 +- .../sarif-support-for-code-scanning.md | 1 - ...tting-up-code-scanning-for-a-repository.md | 117 +++++++++++++ ...g-code-scanning-alerts-in-pull-requests.md | 2 +- ...bout-alerts-for-vulnerable-dependencies.md | 7 +- ...ilities-in-the-github-advisory-database.md | 43 +++-- .../about-billing-for-github-actions.md | 2 + .../about-billing-for-github-packages.md | 2 + ...-your-spending-limit-for-github-actions.md | 2 + ...your-spending-limit-for-github-packages.md | 2 + ...analysis-settings-for-your-organization.md | 29 ++-- ...y-permission-levels-for-an-organization.md | 6 +- ...n-azure-subscription-to-your-enterprise.md | 40 +++++ .../index.md | 1 + .../roles-in-an-enterprise.md | 4 +- ...n-and-usage-for-your-enterprise-account.md | 2 + ...on-levels-for-a-user-account-repository.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 4 +- .../creating-a-github-pages-site.md | 4 +- .../de-DE/content/rest/overview/libraries.md | 6 +- .../overview/resources-in-the-rest-api.md | 8 +- .../de-DE/content/rest/reference/repos.md | 2 +- .../data/reusables/actions/enterprise-beta.md | 7 +- .../actions/enterprise-common-prereqs.md | 2 +- .../enterprise-hardware-considerations.md | 2 +- .../note-org-enable-uses-seats.md | 4 +- .../code-scanning/enabling-options.md | 4 +- .../dependabot/supported-package-managers.md | 4 +- .../desktop/choose-clone-repository.md | 12 ++ .../reusables/desktop/choose-local-path.md | 13 ++ .../data/reusables/desktop/click-clone.md | 14 ++ .../reusables/desktop/cloning-location-tab.md | 12 ++ .../desktop/cloning-repository-list.md | 13 ++ .../reusables/desktop/fork-type-prompt.md | 42 +++++ .../desktop/open-repository-settings.md | 14 ++ .../reusables/desktop/select-fork-behavior.md | 28 ++++ .../billing-microsoft-ea-overview.md | 1 + .../payment-information-tab.md | 1 + .../about-adjusting-resources.md | 1 + .../aws-supported-instance-types.md | 48 ++---- .../hardware-considerations-all-platforms.md | 22 +-- .../hardware-rec-table.md | 38 ++--- .../reusables/gated-features/auto-merge.md | 2 +- .../reusables/gated-features/code-scanning.md | 5 +- .../supported-github-runners.md | 16 +- .../github-actions/ubuntu-runner-preview.md | 2 +- .../organizations/organizations_include.md | 1 + .../reusables/pages/new-or-existing-repo.md | 2 + .../pull_requests/you-can-auto-merge.md | 4 +- .../pull_request_webhook_properties.md | 6 +- .../data/variables/action_code_examples.yml | 8 +- translations/de-DE/data/variables/product.yml | 10 +- .../about-self-hosted-runners.md | 10 +- ...using-self-hosted-runners-in-a-workflow.md | 2 +- ...pecifications-for-github-hosted-runners.md | 15 +- ...guring-code-scanning-for-your-appliance.md | 2 +- ...ing-data-encryption-for-your-enterprise.md | 14 +- .../upgrading-github-enterprise-server.md | 20 +++ ...ub-actions-for-github-enterprise-server.md | 38 +++-- ...orking-repositories-from-github-desktop.md | 44 ++--- .../managing-tags.md | 6 +- .../apps/activating-beta-features-for-apps.md | 2 + .../apps/authenticating-with-github-apps.md | 2 +- .../creating-ci-tests-with-the-checks-api.md | 14 +- .../migrating-oauth-apps-to-github-apps.md | 4 +- ...refreshing-user-to-server-access-tokens.md | 2 +- .../suspending-a-github-app-installation.md | 2 + .../handling-new-purchases-and-free-trials.md | 18 +- ...bout-using-replit-with-github-classroom.md | 2 +- .../about-dependabot-version-updates.md | 5 +- .../about-protected-branches.md | 4 +- .../about-securing-your-repository.md | 18 +- ...g-secret-scanning-for-your-repositories.md | 6 +- ...ge-for-pull-requests-in-your-repository.md | 5 +- ...d-analysis-settings-for-your-repository.md | 11 +- .../securing-your-repository.md | 1 + .../setting-repository-visibility.md | 2 +- .../associating-an-email-with-your-gpg-key.md | 10 +- .../automatically-merging-a-pull-request.md | 3 +- .../merging-a-pull-request.md | 1 - .../about-code-owners.md | 2 +- ...-codeql-code-scanning-in-your-ci-system.md | 29 ++-- ...-codeql-workflow-for-compiled-languages.md | 2 +- .../index.md | 2 +- ...ode-scanning-alerts-for-your-repository.md | 8 +- ...-codeql-code-scanning-in-your-ci-system.md | 2 +- ...tting-up-code-scanning-for-a-repository.md | 121 ++++++++++++++ ...g-code-scanning-alerts-in-pull-requests.md | 2 +- ...bout-alerts-for-vulnerable-dependencies.md | 7 +- ...ilities-in-the-github-advisory-database.md | 23 ++- .../about-billing-for-github-actions.md | 2 + .../about-billing-for-github-packages.md | 2 + ...-your-spending-limit-for-github-actions.md | 2 + ...your-spending-limit-for-github-packages.md | 2 + ...analysis-settings-for-your-organization.md | 29 ++-- ...y-permission-levels-for-an-organization.md | 6 +- ...n-azure-subscription-to-your-enterprise.md | 40 +++++ .../index.md | 1 + .../roles-in-an-enterprise.md | 4 +- ...n-and-usage-for-your-enterprise-account.md | 2 + ...on-levels-for-a-user-account-repository.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 4 +- .../creating-a-github-pages-site.md | 4 +- .../es-ES/content/rest/overview/libraries.md | 8 +- .../overview/resources-in-the-rest-api.md | 8 +- .../es-ES/content/rest/reference/repos.md | 2 +- .../data/reusables/actions/enterprise-beta.md | 7 +- .../actions/enterprise-common-prereqs.md | 2 +- .../enterprise-hardware-considerations.md | 2 +- .../note-org-enable-uses-seats.md | 4 +- .../code-scanning/enabling-options.md | 4 +- .../dependabot/supported-package-managers.md | 4 +- .../desktop/choose-clone-repository.md | 12 ++ .../reusables/desktop/choose-local-path.md | 13 ++ .../data/reusables/desktop/click-clone.md | 14 ++ .../reusables/desktop/cloning-location-tab.md | 12 ++ .../desktop/cloning-repository-list.md | 13 ++ .../reusables/desktop/fork-type-prompt.md | 42 +++++ .../desktop/open-repository-settings.md | 14 ++ .../reusables/desktop/select-fork-behavior.md | 28 ++++ .../billing-microsoft-ea-overview.md | 1 + .../payment-information-tab.md | 1 + .../about-adjusting-resources.md | 1 + .../aws-supported-instance-types.md | 48 ++---- .../hardware-considerations-all-platforms.md | 22 +-- .../hardware-rec-table.md | 38 ++--- .../reusables/gated-features/auto-merge.md | 2 +- .../reusables/gated-features/code-scanning.md | 5 +- .../supported-github-runners.md | 16 +- .../github-actions/ubuntu-runner-preview.md | 2 +- .../organizations/organizations_include.md | 1 + .../reusables/pages/new-or-existing-repo.md | 2 + .../pull_requests/you-can-auto-merge.md | 4 +- .../pull_request_webhook_properties.md | 6 +- .../data/variables/action_code_examples.yml | 8 +- translations/es-ES/data/variables/product.yml | 10 +- .../about-self-hosted-runners.md | 14 +- ...using-self-hosted-runners-in-a-workflow.md | 2 +- ...pecifications-for-github-hosted-runners.md | 15 +- ...guring-code-scanning-for-your-appliance.md | 2 +- ...ing-data-encryption-for-your-enterprise.md | 14 +- .../upgrading-github-enterprise-server.md | 20 +++ ...ub-actions-for-github-enterprise-server.md | 34 +++- ...izing-user-messages-for-your-enterprise.md | 2 +- .../user-management/managing-dormant-users.md | 4 +- .../managing-global-webhooks.md | 4 +- ...naging-organizations-in-your-enterprise.md | 2 +- ...anaging-repositories-in-your-enterprise.md | 2 +- .../managing-users-in-your-enterprise.md | 2 +- .../migrating-data-to-your-enterprise.md | 2 +- .../migrating-to-internal-repositories.md | 2 +- ...-a-legal-hold-on-a-user-or-organization.md | 2 +- ...nting-users-from-creating-organizations.md | 2 +- ...ctor-authentication-for-an-organization.md | 2 +- .../searching-the-audit-log.md | 6 +- .../suspending-and-unsuspending-users.md | 2 +- .../user-management/viewing-push-logs.md | 6 +- ...orking-repositories-from-github-desktop.md | 44 ++--- .../managing-tags.md | 6 +- .../apps/activating-beta-features-for-apps.md | 2 + .../apps/authenticating-with-github-apps.md | 2 +- .../creating-ci-tests-with-the-checks-api.md | 14 +- .../migrating-oauth-apps-to-github-apps.md | 4 +- ...refreshing-user-to-server-access-tokens.md | 2 +- .../suspending-a-github-app-installation.md | 2 + .../handling-new-purchases-and-free-trials.md | 18 +- .../about-github-education-for-students.md | 4 +- .../about-github-education.md | 2 +- ...n-for-a-student-developer-pack-approved.md | 2 +- ...ducator-or-researcher-discount-approved.md | 2 +- ...bout-using-replit-with-github-classroom.md | 2 +- .../basics-of-setting-up-github-classroom.md | 2 +- .../create-a-group-assignment.md | 26 +-- .../create-an-individual-assignment.md | 18 +- .../about-dependabot-version-updates.md | 5 +- .../about-protected-branches.md | 12 +- .../about-securing-your-repository.md | 18 +- ...g-secret-scanning-for-your-repositories.md | 6 +- ...ge-for-pull-requests-in-your-repository.md | 5 +- ...d-analysis-settings-for-your-repository.md | 11 +- .../securing-your-repository.md | 1 + .../setting-repository-visibility.md | 2 +- .../associating-an-email-with-your-gpg-key.md | 10 +- .../automatically-merging-a-pull-request.md | 3 +- .../merging-a-pull-request.md | 1 - .../about-code-owners.md | 2 +- .../about-code-scanning.md | 35 ++-- ...-codeql-code-scanning-in-your-ci-system.md | 29 ++-- ...-codeql-workflow-for-compiled-languages.md | 2 +- .../index.md | 2 +- ...ode-scanning-alerts-for-your-repository.md | 8 +- ...-codeql-code-scanning-in-your-ci-system.md | 2 +- .../sarif-support-for-code-scanning.md | 1 - ...tting-up-code-scanning-for-a-repository.md | 117 +++++++++++++ ...g-code-scanning-alerts-in-pull-requests.md | 2 +- ...ilities-in-the-github-advisory-database.md | 43 +++-- .../about-billing-for-github-actions.md | 2 + .../about-billing-for-github-packages.md | 2 + ...-your-spending-limit-for-github-actions.md | 4 +- ...your-spending-limit-for-github-packages.md | 2 + ...analysis-settings-for-your-organization.md | 29 ++-- ...y-permission-levels-for-an-organization.md | 6 +- ...n-azure-subscription-to-your-enterprise.md | 40 +++++ .../index.md | 1 + .../roles-in-an-enterprise.md | 4 +- ...n-and-usage-for-your-enterprise-account.md | 2 + ...on-levels-for-a-user-account-repository.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 4 +- .../creating-a-github-pages-site.md | 4 +- .../managing-available-metrics-and-reports.md | 14 +- .../ja-JP/content/rest/overview/libraries.md | 8 +- .../overview/resources-in-the-rest-api.md | 8 +- .../ja-JP/content/rest/reference/repos.md | 2 +- .../ja-JP/data/glossaries/external.yml | 2 +- .../ja-JP/data/release-notes/2-21/0.yml | 42 ++--- .../ja-JP/data/release-notes/2-21/1.yml | 26 +-- .../ja-JP/data/release-notes/2-21/10.yml | 16 +- .../ja-JP/data/release-notes/2-21/11.yml | 22 +-- .../ja-JP/data/release-notes/2-21/12.yml | 18 +- .../ja-JP/data/release-notes/2-21/13.yml | 26 +-- .../ja-JP/data/release-notes/2-21/14.yml | 14 +- .../ja-JP/data/release-notes/2-21/2.yml | 26 +-- .../ja-JP/data/release-notes/2-21/3.yml | 20 +-- .../ja-JP/data/release-notes/2-21/4.yml | 40 ++--- .../ja-JP/data/release-notes/2-21/5.yml | 18 +- .../ja-JP/data/release-notes/2-21/7.yml | 16 +- .../ja-JP/data/release-notes/2-21/8.yml | 18 +- .../ja-JP/data/release-notes/2-21/9.yml | 42 ++--- .../ja-JP/data/release-notes/2-22/0.yml | 150 ++++++++--------- .../ja-JP/data/release-notes/2-22/1.yml | 80 ++++----- .../ja-JP/data/release-notes/2-22/2.yml | 32 ++-- .../ja-JP/data/release-notes/2-22/3.yml | 28 ++-- .../ja-JP/data/release-notes/2-22/4.yml | 20 +-- .../ja-JP/data/release-notes/2-22/5.yml | 34 ++-- .../ja-JP/data/release-notes/2-22/6.yml | 24 +-- .../ja-JP/data/release-notes/3-0/0-rc1.yml | 156 +++++++++--------- .../ja-JP/data/release-notes/3-0/0-rc2.yml | 30 ++-- .../data/reusables/actions/enterprise-beta.md | 7 +- .../actions/enterprise-common-prereqs.md | 2 +- .../enterprise-hardware-considerations.md | 2 +- .../note-org-enable-uses-seats.md | 4 +- .../code-scanning/enabling-options.md | 4 +- .../dependabot/supported-package-managers.md | 4 +- .../desktop/choose-clone-repository.md | 12 ++ .../reusables/desktop/choose-local-path.md | 13 ++ .../data/reusables/desktop/click-clone.md | 14 ++ .../reusables/desktop/cloning-location-tab.md | 12 ++ .../desktop/cloning-repository-list.md | 13 ++ .../reusables/desktop/fork-type-prompt.md | 42 +++++ .../desktop/open-repository-settings.md | 14 ++ .../reusables/desktop/select-fork-behavior.md | 28 ++++ .../reusables/education/apply-for-team.md | 2 +- .../billing-microsoft-ea-overview.md | 1 + .../enterprise-accounts/hooks-tab.md | 3 +- .../enterprise-accounts/messages-tab.md | 3 +- .../payment-information-tab.md | 1 + .../about-adjusting-resources.md | 1 + .../aws-supported-instance-types.md | 48 ++---- .../hardware-considerations-all-platforms.md | 24 +-- .../hardware-rec-table.md | 38 ++--- .../reusables/gated-features/auto-merge.md | 2 +- .../reusables/gated-features/code-scanning.md | 5 +- .../supported-github-runners.md | 16 +- .../github-actions/ubuntu-runner-preview.md | 2 +- .../reusables/github-insights/events-tab.md | 3 +- .../github-insights/exclude-files-tab.md | 3 +- .../github-insights/repo-groups-tab.md | 3 +- .../github-insights/repositories-tab.md | 3 +- .../reusables/github-insights/settings-tab.md | 3 +- .../reusables/github-insights/teams-tab.md | 3 +- .../organizations/organizations_include.md | 1 + .../reusables/pages/new-or-existing-repo.md | 2 + .../pull_requests/you-can-auto-merge.md | 4 +- .../pull_request_webhook_properties.md | 6 +- .../data/variables/action_code_examples.yml | 8 +- translations/ja-JP/data/variables/product.yml | 10 +- .../about-self-hosted-runners.md | 12 +- ...using-self-hosted-runners-in-a-workflow.md | 2 +- ...pecifications-for-github-hosted-runners.md | 15 +- ...guring-code-scanning-for-your-appliance.md | 2 +- ...ing-data-encryption-for-your-enterprise.md | 14 +- .../upgrading-github-enterprise-server.md | 20 +++ ...ub-actions-for-github-enterprise-server.md | 34 +++- ...orking-repositories-from-github-desktop.md | 44 ++--- .../managing-tags.md | 6 +- .../apps/activating-beta-features-for-apps.md | 2 + .../apps/authenticating-with-github-apps.md | 2 +- .../creating-ci-tests-with-the-checks-api.md | 6 +- .../migrating-oauth-apps-to-github-apps.md | 4 +- ...refreshing-user-to-server-access-tokens.md | 2 +- .../suspending-a-github-app-installation.md | 2 + .../handling-new-purchases-and-free-trials.md | 18 +- ...bout-using-replit-with-github-classroom.md | 2 +- .../about-dependabot-version-updates.md | 5 +- .../about-protected-branches.md | 6 +- .../about-securing-your-repository.md | 18 +- ...g-secret-scanning-for-your-repositories.md | 6 +- ...ge-for-pull-requests-in-your-repository.md | 5 +- ...d-analysis-settings-for-your-repository.md | 11 +- .../securing-your-repository.md | 1 + .../setting-repository-visibility.md | 2 +- .../associating-an-email-with-your-gpg-key.md | 10 +- .../automatically-merging-a-pull-request.md | 3 +- .../merging-a-pull-request.md | 1 - .../about-code-owners.md | 2 +- .../about-code-scanning.md | 2 +- .../configuring-code-scanning.md | 6 +- ...-codeql-code-scanning-in-your-ci-system.md | 29 ++-- ...-codeql-workflow-for-compiled-languages.md | 2 +- .../index.md | 2 +- ...ode-scanning-alerts-for-your-repository.md | 8 +- ...-codeql-code-scanning-in-your-ci-system.md | 2 +- .../sarif-support-for-code-scanning.md | 1 - ...tting-up-code-scanning-for-a-repository.md | 117 +++++++++++++ ...g-code-scanning-alerts-in-pull-requests.md | 2 +- ...bout-alerts-for-vulnerable-dependencies.md | 7 +- ...ilities-in-the-github-advisory-database.md | 43 +++-- .../about-billing-for-github-actions.md | 2 + .../about-billing-for-github-packages.md | 2 + ...-your-spending-limit-for-github-actions.md | 2 + ...your-spending-limit-for-github-packages.md | 2 + ...analysis-settings-for-your-organization.md | 29 ++-- ...y-permission-levels-for-an-organization.md | 6 +- ...n-azure-subscription-to-your-enterprise.md | 40 +++++ .../index.md | 1 + .../roles-in-an-enterprise.md | 4 +- ...n-and-usage-for-your-enterprise-account.md | 2 + ...on-levels-for-a-user-account-repository.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 4 +- .../creating-a-github-pages-site.md | 4 +- .../ko-KR/content/rest/overview/libraries.md | 6 +- .../overview/resources-in-the-rest-api.md | 8 +- .../ko-KR/content/rest/reference/repos.md | 2 +- .../data/reusables/actions/enterprise-beta.md | 7 +- .../actions/enterprise-common-prereqs.md | 2 +- .../enterprise-hardware-considerations.md | 2 +- .../note-org-enable-uses-seats.md | 4 +- .../code-scanning/enabling-options.md | 4 +- .../dependabot/supported-package-managers.md | 4 +- .../desktop/choose-clone-repository.md | 12 ++ .../reusables/desktop/choose-local-path.md | 13 ++ .../data/reusables/desktop/click-clone.md | 14 ++ .../reusables/desktop/cloning-location-tab.md | 12 ++ .../desktop/cloning-repository-list.md | 13 ++ .../reusables/desktop/fork-type-prompt.md | 42 +++++ .../desktop/open-repository-settings.md | 14 ++ .../reusables/desktop/select-fork-behavior.md | 28 ++++ .../billing-microsoft-ea-overview.md | 1 + .../payment-information-tab.md | 1 + .../about-adjusting-resources.md | 1 + .../aws-supported-instance-types.md | 48 ++---- .../hardware-considerations-all-platforms.md | 22 +-- .../hardware-rec-table.md | 38 ++--- .../reusables/gated-features/auto-merge.md | 2 +- .../reusables/gated-features/code-scanning.md | 5 +- .../supported-github-runners.md | 16 +- .../github-actions/ubuntu-runner-preview.md | 2 +- .../organizations/organizations_include.md | 1 + .../reusables/pages/new-or-existing-repo.md | 2 + .../pull_requests/you-can-auto-merge.md | 4 +- .../pull_request_webhook_properties.md | 6 +- .../data/variables/action_code_examples.yml | 8 +- translations/ko-KR/data/variables/product.yml | 10 +- .../guides/about-service-containers.md | 2 +- .../creating-postgresql-service-containers.md | 2 +- .../creating-redis-service-containers.md | 2 +- ...ing-to-amazon-elastic-container-service.md | 2 +- .../guides/deploying-to-azure-app-service.md | 2 +- .../deploying-to-google-kubernetes-engine.md | 2 +- .../about-self-hosted-runners.md | 10 +- ...using-self-hosted-runners-in-a-workflow.md | 2 +- ...pecifications-for-github-hosted-runners.md | 15 +- ...guring-code-scanning-for-your-appliance.md | 2 +- ...ing-data-encryption-for-your-enterprise.md | 14 +- .../upgrading-github-enterprise-server.md | 20 +++ ...ub-actions-for-github-enterprise-server.md | 34 +++- ...orking-repositories-from-github-desktop.md | 44 ++--- .../managing-tags.md | 6 +- .../apps/activating-beta-features-for-apps.md | 2 + .../apps/authenticating-with-github-apps.md | 4 +- .../creating-ci-tests-with-the-checks-api.md | 6 +- .../migrating-oauth-apps-to-github-apps.md | 4 +- ...refreshing-user-to-server-access-tokens.md | 2 +- .../suspending-a-github-app-installation.md | 2 + .../handling-new-purchases-and-free-trials.md | 18 +- .../pt-BR/content/discussions/quickstart.md | 2 +- ...bout-using-replit-with-github-classroom.md | 2 +- .../about-dependabot-version-updates.md | 3 +- .../about-securing-your-repository.md | 18 +- ...g-secret-scanning-for-your-repositories.md | 6 +- ...ge-for-pull-requests-in-your-repository.md | 5 +- ...d-analysis-settings-for-your-repository.md | 11 +- .../securing-your-repository.md | 1 + .../associating-an-email-with-your-gpg-key.md | 10 +- .../automatically-merging-a-pull-request.md | 3 +- .../creating-a-pull-request.md | 6 +- .../merging-a-pull-request.md | 1 - .../about-code-owners.md | 2 +- ...-codeql-code-scanning-in-your-ci-system.md | 29 ++-- ...-codeql-workflow-for-compiled-languages.md | 2 +- .../index.md | 2 +- ...ode-scanning-alerts-for-your-repository.md | 8 +- ...-codeql-code-scanning-in-your-ci-system.md | 2 +- .../sarif-support-for-code-scanning.md | 1 - ...tting-up-code-scanning-for-a-repository.md | 117 +++++++++++++ ...g-code-scanning-alerts-in-pull-requests.md | 2 +- ...ilities-in-the-github-advisory-database.md | 43 +++-- .../about-billing-for-github-actions.md | 6 +- .../about-billing-for-github-packages.md | 2 + ...-your-spending-limit-for-github-actions.md | 2 + ...your-spending-limit-for-github-packages.md | 2 + ...analysis-settings-for-your-organization.md | 29 ++-- ...y-permission-levels-for-an-organization.md | 6 +- ...n-azure-subscription-to-your-enterprise.md | 40 +++++ .../index.md | 1 + .../roles-in-an-enterprise.md | 4 +- ...n-and-usage-for-your-enterprise-account.md | 2 + .../site-policy/github-and-trade-controls.md | 10 +- .../github-subprocessors-and-cookies.md | 98 +++++------ .../creating-a-github-pages-site.md | 4 +- .../pt-BR/content/rest/overview/libraries.md | 8 +- .../overview/resources-in-the-rest-api.md | 8 +- .../pt-BR/data/release-notes/2-20/0.yml | 4 +- .../pt-BR/data/release-notes/2-20/1.yml | 4 +- .../pt-BR/data/release-notes/2-20/10.yml | 4 +- .../pt-BR/data/release-notes/2-20/11.yml | 4 +- .../pt-BR/data/release-notes/2-20/12.yml | 4 +- .../pt-BR/data/release-notes/2-20/13.yml | 4 +- .../pt-BR/data/release-notes/2-20/14.yml | 4 +- .../pt-BR/data/release-notes/2-20/16.yml | 4 +- .../pt-BR/data/release-notes/2-20/17.yml | 4 +- .../pt-BR/data/release-notes/2-20/18.yml | 4 +- .../pt-BR/data/release-notes/2-20/19.yml | 4 +- .../pt-BR/data/release-notes/2-20/2.yml | 4 +- .../pt-BR/data/release-notes/2-20/20.yml | 4 +- .../pt-BR/data/release-notes/2-20/21.yml | 4 +- .../pt-BR/data/release-notes/2-20/22.yml | 4 +- .../pt-BR/data/release-notes/2-20/23.yml | 4 +- .../pt-BR/data/release-notes/2-20/3.yml | 4 +- .../pt-BR/data/release-notes/2-20/4.yml | 4 +- .../pt-BR/data/release-notes/2-20/5.yml | 4 +- .../pt-BR/data/release-notes/2-20/6.yml | 4 +- .../pt-BR/data/release-notes/2-20/7.yml | 4 +- .../pt-BR/data/release-notes/2-20/8.yml | 4 +- .../pt-BR/data/release-notes/2-20/9.yml | 4 +- .../pt-BR/data/release-notes/2-21/0.yml | 102 ++++++------ .../pt-BR/data/release-notes/2-21/1.yml | 6 +- .../pt-BR/data/release-notes/2-21/10.yml | 6 +- .../pt-BR/data/release-notes/2-21/11.yml | 4 +- .../pt-BR/data/release-notes/2-21/12.yml | 4 +- .../pt-BR/data/release-notes/2-21/13.yml | 4 +- .../pt-BR/data/release-notes/2-21/14.yml | 4 +- .../pt-BR/data/release-notes/2-21/2.yml | 6 +- .../pt-BR/data/release-notes/2-21/3.yml | 6 +- .../pt-BR/data/release-notes/2-21/4.yml | 18 +- .../pt-BR/data/release-notes/2-21/5.yml | 6 +- .../pt-BR/data/release-notes/2-21/7.yml | 6 +- .../pt-BR/data/release-notes/2-21/8.yml | 6 +- .../pt-BR/data/release-notes/2-21/9.yml | 6 +- .../pt-BR/data/release-notes/2-22/0.yml | 64 +++---- .../pt-BR/data/release-notes/2-22/1.yml | 16 +- .../pt-BR/data/release-notes/2-22/2.yml | 26 +-- .../pt-BR/data/release-notes/2-22/3.yml | 10 +- .../pt-BR/data/release-notes/2-22/4.yml | 4 +- .../pt-BR/data/release-notes/2-22/5.yml | 4 +- .../pt-BR/data/release-notes/2-22/6.yml | 12 +- .../pt-BR/data/release-notes/3-0/0-rc1.yml | 150 ++++++++--------- .../pt-BR/data/release-notes/3-0/0-rc2.yml | 30 ++-- .../reusables/actions/actions-not-verified.md | 2 +- .../actions-packages-set-spending-limit.md | 2 +- .../actions/enterprise-actions-permissions.md | 6 +- .../data/reusables/actions/enterprise-beta.md | 7 +- .../actions/enterprise-common-prereqs.md | 4 +- .../actions/enterprise-enable-checkbox.md | 2 +- .../enterprise-hardware-considerations.md | 2 +- .../actions/enterprise-http-proxy.md | 2 +- .../actions/enterprise-limit-actions-use.md | 2 +- .../enterprise-postinstall-nextsteps.md | 2 +- .../actions/enterprise-s3-permission.md | 2 +- .../actions/enterprise-s3-support-warning.md | 2 +- .../actions/enterprise-self-signed-cert.md | 2 +- .../actions/enterprise-storage-ha-backups.md | 2 +- .../reusables/actions/environments-beta.md | 2 +- .../reusables/actions/visualization-beta.md | 2 +- .../actions/workflow-template-overview.md | 2 +- .../note-org-enable-uses-seats.md | 4 +- .../reusables/audit_log/audit-log-api-info.md | 10 +- .../audit-log-git-events-retention.md | 2 +- .../reusables/classroom/about-assignments.md | 2 +- .../reusables/classroom/about-autograding.md | 2 +- .../reusables/classroom/about-classrooms.md | 2 +- .../reusables/classroom/about-online-ides.md | 2 +- .../assignments-classroom-prerequisite.md | 2 +- .../classroom/assignments-click-pencil.md | 2 +- .../classroom/assignments-group-definition.md | 2 +- .../assignments-guide-assign-a-deadline.md | 4 +- .../assignments-guide-choose-an-online-ide.md | 4 +- ...nments-guide-choose-template-repository.md | 4 +- .../assignments-guide-choose-visibility.md | 8 +- ...ments-guide-click-continue-after-basics.md | 4 +- ...ontinue-after-starter-code-and-feedback.md | 4 +- ...ts-guide-click-create-assignment-button.md | 4 +- ...nments-guide-create-review-pull-request.md | 4 +- ...assignments-guide-create-the-assignment.md | 4 +- ...assignments-guide-intro-for-environment.md | 2 +- .../assignments-guide-prevent-changes.md | 6 +- .../assignments-guide-using-autograding.md | 14 +- .../assignments-individual-definition.md | 2 +- .../assignments-to-prevent-submission.md | 2 +- .../classroom/assignments-type-a-title.md | 4 +- .../classroom-creates-group-repositories.md | 2 +- ...assroom-creates-individual-repositories.md | 2 +- .../classroom-enables-invitation-urls.md | 2 +- .../classroom/click-assignment-in-list.md | 2 +- .../classroom/click-classroom-in-list.md | 2 +- .../reusables/classroom/click-settings.md | 2 +- .../reusables/classroom/click-students.md | 2 +- .../classroom/guide-create-new-classroom.md | 6 +- .../classroom/invitation-url-warning.md | 2 +- .../readme-contains-button-for-online-ide.md | 2 +- .../classroom/sign-into-github-classroom.md | 2 +- ...-test-drop-down-to-click-grading-method.md | 2 +- .../you-can-choose-a-template-repository.md | 2 +- ...-can-create-a-pull-request-for-feedback.md | 2 +- .../data/reusables/code-scanning/beta.md | 2 +- .../code-scanning/enabling-options.md | 4 +- .../example-configuration-files.md | 2 +- .../reusables/code-scanning/not-available.md | 2 +- .../code-scanning/upload-sarif-alert-limit.md | 2 +- .../dependabot/private-dependencies-note.md | 4 +- .../dependabot/supported-package-managers.md | 58 +++---- .../desktop/choose-clone-repository.md | 12 ++ .../reusables/desktop/choose-local-path.md | 13 ++ .../data/reusables/desktop/click-clone.md | 14 ++ .../reusables/desktop/cloning-location-tab.md | 12 ++ .../desktop/cloning-repository-list.md | 13 ++ .../data/reusables/desktop/delete-tag.md | 6 +- .../reusables/desktop/fork-type-prompt.md | 42 +++++ .../desktop/open-repository-settings.md | 14 ++ .../reusables/desktop/select-fork-behavior.md | 28 ++++ .../pull_request_forked_repos_link.md | 2 +- .../about-categories-and-formats.md | 2 +- .../discussions/about-discussions.md | 2 +- .../discussions/click-discussion-in-list.md | 2 +- .../reusables/discussions/discussions-tab.md | 2 +- .../reusables/discussions/edit-categories.md | 2 +- .../discussions/edit-category-details.md | 2 +- ...-github-discussions-for-your-repository.md | 4 +- .../discussions/github-recognizes-members.md | 2 +- .../marking-a-comment-as-an-answer.md | 16 +- .../discussions/repository-category-limit.md | 2 +- .../discussions/starting-a-discussion.md | 8 +- .../you-can-categorize-discussions.md | 2 +- .../discussions/you-can-convert-an-issue.md | 2 +- .../discussions/you-can-use-discussions.md | 2 +- .../you-cannot-convert-a-discussion.md | 2 +- .../education/click-get-teacher-benefits.md | 2 +- .../education/educator-requirements.md | 4 +- .../billing-microsoft-ea-overview.md | 1 + .../payment-information-tab.md | 1 + .../user-provisioning-release-stage.md | 2 +- .../verified-domains-tab.md | 2 +- .../verifying-domains-release-phase.md | 2 +- .../about-adjusting-resources.md | 1 + .../aws-supported-instance-types.md | 48 ++---- .../hardware-considerations-all-platforms.md | 24 +-- .../hardware-rec-table.md | 38 ++--- .../image-urls-viewable-warning.md | 2 +- .../enterprise_management_console/actions.md | 2 +- .../advanced-security-license.md | 2 +- .../ready-to-import-migrations.md | 2 +- .../message-preview-save.md | 2 +- .../reusables/gated-features/auto-merge.md | 2 +- .../reusables/gated-features/code-scanning.md | 5 +- .../reusables/gated-features/discussions.md | 2 +- .../reusables/gated-features/environments.md | 2 +- .../data/reusables/gated-features/pages.md | 2 +- .../reusables/gated-features/private-pages.md | 2 +- .../gated-features/protected-branches.md | 2 +- .../cannot-convert-public-gists-to-secret.md | 2 +- .../github-actions/actions-billing.md | 2 +- .../actions-spending-limit-brief.md | 2 +- .../actions-spending-limit-detailed.md | 2 +- .../github-actions/contacting-support.md | 2 +- .../supported-github-runners.md | 16 +- .../github-actions/ubuntu-runner-preview.md | 2 +- .../organizations/organizations_include.md | 1 + .../reusables/pages/new-or-existing-repo.md | 2 + .../pages/private_pages_are_public_warning.md | 2 +- .../pull_requests/you-can-auto-merge.md | 4 +- .../pull_request_webhook_properties.md | 6 +- .../data/variables/action_code_examples.yml | 22 +-- translations/pt-BR/data/variables/product.yml | 10 +- .../about-self-hosted-runners.md | 12 +- ...using-self-hosted-runners-in-a-workflow.md | 2 +- ...pecifications-for-github-hosted-runners.md | 15 +- ...guring-code-scanning-for-your-appliance.md | 2 +- ...ing-data-encryption-for-your-enterprise.md | 14 +- .../upgrading-github-enterprise-server.md | 20 +++ ...ub-actions-for-github-enterprise-server.md | 34 +++- ...orking-repositories-from-github-desktop.md | 44 ++--- .../managing-tags.md | 6 +- .../apps/activating-beta-features-for-apps.md | 2 + .../apps/authenticating-with-github-apps.md | 2 +- .../creating-ci-tests-with-the-checks-api.md | 6 +- .../migrating-oauth-apps-to-github-apps.md | 4 +- ...refreshing-user-to-server-access-tokens.md | 2 +- .../suspending-a-github-app-installation.md | 2 + .../handling-new-purchases-and-free-trials.md | 18 +- ...bout-using-replit-with-github-classroom.md | 2 +- .../about-dependabot-version-updates.md | 5 +- .../about-protected-branches.md | 6 +- .../about-securing-your-repository.md | 18 +- ...g-secret-scanning-for-your-repositories.md | 6 +- ...ge-for-pull-requests-in-your-repository.md | 5 +- ...d-analysis-settings-for-your-repository.md | 11 +- .../securing-your-repository.md | 1 + .../setting-repository-visibility.md | 2 +- .../associating-an-email-with-your-gpg-key.md | 10 +- .../automatically-merging-a-pull-request.md | 3 +- .../merging-a-pull-request.md | 1 - .../about-code-owners.md | 2 +- .../about-code-scanning.md | 2 +- .../configuring-code-scanning.md | 6 +- ...-codeql-code-scanning-in-your-ci-system.md | 29 ++-- ...-codeql-workflow-for-compiled-languages.md | 2 +- .../index.md | 2 +- ...ode-scanning-alerts-for-your-repository.md | 8 +- ...-codeql-code-scanning-in-your-ci-system.md | 2 +- .../sarif-support-for-code-scanning.md | 1 - ...tting-up-code-scanning-for-a-repository.md | 117 +++++++++++++ ...g-code-scanning-alerts-in-pull-requests.md | 2 +- ...bout-alerts-for-vulnerable-dependencies.md | 7 +- ...ilities-in-the-github-advisory-database.md | 43 +++-- .../about-billing-for-github-actions.md | 2 + .../about-billing-for-github-packages.md | 2 + ...-your-spending-limit-for-github-actions.md | 2 + ...your-spending-limit-for-github-packages.md | 2 + ...analysis-settings-for-your-organization.md | 29 ++-- ...y-permission-levels-for-an-organization.md | 6 +- ...n-azure-subscription-to-your-enterprise.md | 40 +++++ .../index.md | 1 + .../roles-in-an-enterprise.md | 4 +- ...n-and-usage-for-your-enterprise-account.md | 2 + ...on-levels-for-a-user-account-repository.md | 2 +- ...reating-a-github-pages-site-with-jekyll.md | 4 +- .../creating-a-github-pages-site.md | 4 +- .../ru-RU/content/rest/overview/libraries.md | 6 +- .../overview/resources-in-the-rest-api.md | 8 +- .../ru-RU/content/rest/reference/repos.md | 2 +- .../data/reusables/actions/enterprise-beta.md | 7 +- .../actions/enterprise-common-prereqs.md | 2 +- .../enterprise-hardware-considerations.md | 2 +- .../note-org-enable-uses-seats.md | 4 +- .../code-scanning/enabling-options.md | 4 +- .../dependabot/supported-package-managers.md | 4 +- .../desktop/choose-clone-repository.md | 12 ++ .../reusables/desktop/choose-local-path.md | 13 ++ .../data/reusables/desktop/click-clone.md | 14 ++ .../reusables/desktop/cloning-location-tab.md | 12 ++ .../desktop/cloning-repository-list.md | 13 ++ .../reusables/desktop/fork-type-prompt.md | 42 +++++ .../desktop/open-repository-settings.md | 14 ++ .../reusables/desktop/select-fork-behavior.md | 28 ++++ .../billing-microsoft-ea-overview.md | 1 + .../payment-information-tab.md | 1 + .../about-adjusting-resources.md | 1 + .../aws-supported-instance-types.md | 48 ++---- .../hardware-considerations-all-platforms.md | 22 +-- .../hardware-rec-table.md | 38 ++--- .../reusables/gated-features/auto-merge.md | 2 +- .../reusables/gated-features/code-scanning.md | 5 +- .../supported-github-runners.md | 16 +- .../github-actions/ubuntu-runner-preview.md | 2 +- .../organizations/organizations_include.md | 1 + .../reusables/pages/new-or-existing-repo.md | 2 + .../pull_requests/you-can-auto-merge.md | 4 +- .../pull_request_webhook_properties.md | 6 +- .../data/variables/action_code_examples.yml | 8 +- translations/ru-RU/data/variables/product.yml | 10 +- .../creating-a-docker-container-action.md | 6 +- .../metadata-syntax-for-github-actions.md | 2 +- .../building-and-testing-java-with-gradle.md | 2 +- .../guides/building-and-testing-net.md | 2 +- .../guides/building-and-testing-nodejs.md | 2 +- .../guides/building-and-testing-python.md | 2 +- .../guides/publishing-docker-images.md | 2 +- .../publishing-java-packages-with-gradle.md | 2 +- .../publishing-java-packages-with-maven.md | 2 +- .../guides/publishing-nodejs-packages.md | 14 +- .../about-self-hosted-runners.md | 10 +- ...using-self-hosted-runners-in-a-workflow.md | 16 +- translations/zh-CN/content/actions/index.md | 2 +- .../finding-and-customizing-actions.md | 4 +- .../introduction-to-github-actions.md | 2 +- ...grating-from-circleci-to-github-actions.md | 2 +- ...ting-from-gitlab-cicd-to-github-actions.md | 2 +- ...igrating-from-jenkins-to-github-actions.md | 2 +- ...rating-from-travis-ci-to-github-actions.md | 2 +- .../security-hardening-for-github-actions.md | 2 +- ...haring-workflows-with-your-organization.md | 2 +- .../zh-CN/content/actions/quickstart.md | 4 +- .../reference/authentication-in-a-workflow.md | 24 +-- ...nd-expression-syntax-for-github-actions.md | 12 +- .../reference/environment-variables.md | 8 +- .../events-that-trigger-workflows.md | 10 +- ...pecifications-for-github-hosted-runners.md | 21 ++- .../workflow-commands-for-github-actions.md | 4 +- .../workflow-syntax-for-github-actions.md | 52 +++--- ...guring-code-scanning-for-your-appliance.md | 2 +- ...ing-data-encryption-for-your-enterprise.md | 14 +- .../upgrading-github-enterprise-server.md | 20 +++ ...ub-actions-for-github-enterprise-server.md | 34 +++- ...orking-repositories-from-github-desktop.md | 54 +++--- .../managing-tags.md | 6 +- .../apps/activating-beta-features-for-apps.md | 2 + .../apps/authenticating-with-github-apps.md | 2 +- ...ating-a-github-app-using-url-parameters.md | 10 +- .../creating-ci-tests-with-the-checks-api.md | 6 +- .../migrating-oauth-apps-to-github-apps.md | 4 +- ...refreshing-user-to-server-access-tokens.md | 2 +- .../suspending-a-github-app-installation.md | 2 + .../handling-new-purchases-and-free-trials.md | 18 +- .../webhook-events-and-payloads.md | 2 +- ...bout-using-replit-with-github-classroom.md | 2 +- .../about-dependabot-version-updates.md | 5 +- .../about-protected-branches.md | 10 +- .../about-securing-your-repository.md | 18 +- ...g-secret-scanning-for-your-repositories.md | 6 +- ...ge-for-pull-requests-in-your-repository.md | 5 +- ...d-analysis-settings-for-your-repository.md | 11 +- .../securing-your-repository.md | 1 + .../setting-repository-visibility.md | 2 +- .../associating-an-email-with-your-gpg-key.md | 10 +- .../automatically-merging-a-pull-request.md | 3 +- .../merging-a-pull-request.md | 1 - ...changes-to-your-work-with-pull-requests.md | 2 +- .../about-code-owners.md | 2 +- .../duplicating-a-repository.md | 2 +- .../about-code-scanning.md | 35 ++-- ...-codeql-code-scanning-in-your-ci-system.md | 29 ++-- ...-codeql-workflow-for-compiled-languages.md | 2 +- .../index.md | 2 +- ...ode-scanning-alerts-for-your-repository.md | 8 +- ...-codeql-code-scanning-in-your-ci-system.md | 2 +- .../sarif-support-for-code-scanning.md | 1 - ...tting-up-code-scanning-for-a-repository.md | 117 +++++++++++++ ...g-code-scanning-alerts-in-pull-requests.md | 2 +- ...ilities-in-the-github-advisory-database.md | 43 +++-- .../about-billing-for-github-actions.md | 2 + .../about-billing-for-github-packages.md | 2 + ...-your-spending-limit-for-github-actions.md | 2 + ...your-spending-limit-for-github-packages.md | 2 + ...analysis-settings-for-your-organization.md | 29 ++-- ...y-permission-levels-for-an-organization.md | 6 +- ...n-azure-subscription-to-your-enterprise.md | 40 +++++ .../index.md | 1 + ...n-and-usage-for-your-enterprise-account.md | 2 + ...on-levels-for-a-user-account-repository.md | 24 +-- ...reating-a-github-pages-site-with-jekyll.md | 4 +- .../creating-a-github-pages-site.md | 4 +- .../zh-CN/content/rest/overview/libraries.md | 6 +- .../zh-CN/content/rest/reference/pulls.md | 2 +- .../zh-CN/content/rest/reference/repos.md | 2 +- .../data/reusables/actions/enterprise-beta.md | 7 +- .../actions/enterprise-common-prereqs.md | 2 +- .../enterprise-hardware-considerations.md | 2 +- .../note-org-enable-uses-seats.md | 4 +- .../code-scanning/enabling-options.md | 4 +- .../dependabot/supported-package-managers.md | 60 +++---- .../desktop/choose-clone-repository.md | 12 ++ .../reusables/desktop/choose-local-path.md | 13 ++ .../data/reusables/desktop/click-clone.md | 14 ++ .../reusables/desktop/cloning-location-tab.md | 12 ++ .../desktop/cloning-repository-list.md | 13 ++ .../reusables/desktop/fork-type-prompt.md | 42 +++++ .../desktop/open-repository-settings.md | 14 ++ .../reusables/desktop/select-fork-behavior.md | 28 ++++ .../about-categories-and-formats.md | 2 +- .../discussions/click-discussion-in-list.md | 2 +- .../discussions/github-recognizes-members.md | 2 +- .../you-can-categorize-discussions.md | 2 +- .../discussions/you-can-convert-an-issue.md | 2 +- .../discussions/you-can-use-discussions.md | 2 +- .../billing-microsoft-ea-overview.md | 1 + .../enterprise-administrators.md | 2 +- .../payment-information-tab.md | 1 + .../about-adjusting-resources.md | 1 + .../aws-supported-instance-types.md | 48 ++---- .../hardware-considerations-all-platforms.md | 22 +-- .../hardware-rec-table.md | 38 ++--- .../reusables/gated-features/auto-merge.md | 2 +- .../reusables/gated-features/code-scanning.md | 5 +- .../supported-github-runners.md | 16 +- .../github-actions/ubuntu-runner-preview.md | 2 +- .../organizations/organizations_include.md | 1 + .../reusables/pages/new-or-existing-repo.md | 2 + .../pull_requests/rebase_and_merge_summary.md | 2 +- .../pull_requests/you-can-auto-merge.md | 4 +- .../pull_request_webhook_properties.md | 6 +- translations/zh-CN/data/ui.yml | 2 +- .../data/variables/action_code_examples.yml | 24 +-- translations/zh-CN/data/variables/product.yml | 10 +- 837 files changed, 5899 insertions(+), 3150 deletions(-) create mode 100644 translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md create mode 100644 translations/de-DE/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md create mode 100644 translations/de-DE/data/reusables/desktop/choose-local-path.md create mode 100644 translations/de-DE/data/reusables/desktop/click-clone.md create mode 100644 translations/de-DE/data/reusables/desktop/fork-type-prompt.md create mode 100644 translations/de-DE/data/reusables/desktop/open-repository-settings.md create mode 100644 translations/de-DE/data/reusables/desktop/select-fork-behavior.md create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/payment-information-tab.md create mode 100644 translations/de-DE/data/reusables/enterprise_installation/about-adjusting-resources.md create mode 100644 translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md create mode 100644 translations/es-ES/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md create mode 100644 translations/es-ES/data/reusables/desktop/choose-local-path.md create mode 100644 translations/es-ES/data/reusables/desktop/click-clone.md create mode 100644 translations/es-ES/data/reusables/desktop/fork-type-prompt.md create mode 100644 translations/es-ES/data/reusables/desktop/open-repository-settings.md create mode 100644 translations/es-ES/data/reusables/desktop/select-fork-behavior.md create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md create mode 100644 translations/es-ES/data/reusables/enterprise-accounts/payment-information-tab.md create mode 100644 translations/es-ES/data/reusables/enterprise_installation/about-adjusting-resources.md create mode 100644 translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md create mode 100644 translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md create mode 100644 translations/ja-JP/data/reusables/desktop/choose-local-path.md create mode 100644 translations/ja-JP/data/reusables/desktop/click-clone.md create mode 100644 translations/ja-JP/data/reusables/desktop/fork-type-prompt.md create mode 100644 translations/ja-JP/data/reusables/desktop/open-repository-settings.md create mode 100644 translations/ja-JP/data/reusables/desktop/select-fork-behavior.md create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/payment-information-tab.md create mode 100644 translations/ja-JP/data/reusables/enterprise_installation/about-adjusting-resources.md create mode 100644 translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md create mode 100644 translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md create mode 100644 translations/ko-KR/data/reusables/desktop/choose-local-path.md create mode 100644 translations/ko-KR/data/reusables/desktop/click-clone.md create mode 100644 translations/ko-KR/data/reusables/desktop/fork-type-prompt.md create mode 100644 translations/ko-KR/data/reusables/desktop/open-repository-settings.md create mode 100644 translations/ko-KR/data/reusables/desktop/select-fork-behavior.md create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md create mode 100644 translations/ko-KR/data/reusables/enterprise-accounts/payment-information-tab.md create mode 100644 translations/ko-KR/data/reusables/enterprise_installation/about-adjusting-resources.md create mode 100644 translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md create mode 100644 translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md create mode 100644 translations/pt-BR/data/reusables/desktop/choose-local-path.md create mode 100644 translations/pt-BR/data/reusables/desktop/click-clone.md create mode 100644 translations/pt-BR/data/reusables/desktop/fork-type-prompt.md create mode 100644 translations/pt-BR/data/reusables/desktop/open-repository-settings.md create mode 100644 translations/pt-BR/data/reusables/desktop/select-fork-behavior.md create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md create mode 100644 translations/pt-BR/data/reusables/enterprise-accounts/payment-information-tab.md create mode 100644 translations/pt-BR/data/reusables/enterprise_installation/about-adjusting-resources.md create mode 100644 translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md create mode 100644 translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md create mode 100644 translations/ru-RU/data/reusables/desktop/choose-local-path.md create mode 100644 translations/ru-RU/data/reusables/desktop/click-clone.md create mode 100644 translations/ru-RU/data/reusables/desktop/fork-type-prompt.md create mode 100644 translations/ru-RU/data/reusables/desktop/open-repository-settings.md create mode 100644 translations/ru-RU/data/reusables/desktop/select-fork-behavior.md create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md create mode 100644 translations/ru-RU/data/reusables/enterprise-accounts/payment-information-tab.md create mode 100644 translations/ru-RU/data/reusables/enterprise_installation/about-adjusting-resources.md create mode 100644 translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md create mode 100644 translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md create mode 100644 translations/zh-CN/data/reusables/desktop/choose-local-path.md create mode 100644 translations/zh-CN/data/reusables/desktop/click-clone.md create mode 100644 translations/zh-CN/data/reusables/desktop/fork-type-prompt.md create mode 100644 translations/zh-CN/data/reusables/desktop/open-repository-settings.md create mode 100644 translations/zh-CN/data/reusables/desktop/select-fork-behavior.md create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md create mode 100644 translations/zh-CN/data/reusables/enterprise-accounts/payment-information-tab.md create mode 100644 translations/zh-CN/data/reusables/enterprise_installation/about-adjusting-resources.md 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 75da4a3e35..70bf5b1467 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 @@ -63,7 +63,7 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe {% data reusables.github-actions.usage-api-requests %} - **Auftrags-Matrix** - {% data reusables.github-actions.usage-matrix-limits %} -### Unterstützte Betriebssysteme für selbst-gehostete Runner +### Supported architectures and operating systems for self-hosted runners The following operating systems are supported for the self-hosted runner application. @@ -92,6 +92,14 @@ The following operating systems are supported for the self-hosted runner applica - macOS 10.13 (High Sierra) oder höher +#### Architectures + +The following processor architectures are supported for the self-hosted runner application. + +- `x64` - Linux, macOS, Windows. +- `ARM64` - Linux only. +- `ARM32` - Linux only. + {% if enterpriseServerVersions contains currentVersion %} ### Kommunikation zwischen selbst-gehosteten Runnern und {% data variables.product.prodname_dotcom %} 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 c849f67dae..4822686a24 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 @@ -29,7 +29,7 @@ Ein selbst-gehosteter Runner erhält automatisch bestimmte Labels, wenn er zu {% * `self-hosted`: Standard-Label, welches allen selbst-gehosteten Runnern zugeteilt wird. * `Linux`, `windows`, oder `macOS`: Je nach Betriebssystem zugeteilt. -* `x86`, `x64`, `ARM`oder `ARM64`: Je nach Hardware-Architektur zugeteilt. +* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. Du kannst die YAML Deines Workflows verwenden, um Jobs an eine Kombination dieser Labels zu senden. In diesem Beispiel ist ein selbst-gehosteter Runner, der allen drei Labels entspricht, berechtigt, den Job auszuführen: diff --git a/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md index a48b7494e6..77dcfae8a3 100644 --- a/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md @@ -1,6 +1,6 @@ --- title: Specifications for GitHub-hosted runners -intro: '{% data variables.product.prodname_dotcom %} bietet gehostete virtuelle Maschinen, um Workflows auszuführen. Die virtuelle Maschine umfasst eine Umgebung mit Tools, Paketen und Einstellungen für {% data variables.product.prodname_actions %}.' +intro: '{% data variables.product.prodname_dotcom %} offers hosted virtual machines to run workflows. The virtual machine contains an environment of tools, packages, and settings available for {% data variables.product.prodname_actions %} to use.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/virtual-environments-for-github-actions @@ -17,35 +17,40 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -### Informationen zu {% data variables.product.prodname_dotcom %}-gehosteten Runnern +### About {% data variables.product.prodname_dotcom %}-hosted runners -Ein {% data variables.product.prodname_dotcom %}-gehosteter Runner ist eine virtuelle Maschine, die von {% data variables.product.prodname_dotcom %} gehostet wird und auf der die Runner-Anwendung der {% data variables.product.prodname_actions %} installiert ist. {% data variables.product.prodname_dotcom %} bietet Runner mit den Betriebssystemen Linux, Windows und MacOS. +A {% data variables.product.prodname_dotcom %}-hosted runner is a virtual machine hosted by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner application installed. {% data variables.product.prodname_dotcom %} offers runners with Linux, Windows, and macOS operating systems. -Wenn Du einen {% data variables.product.prodname_dotcom %}-gehosteten Runner verwendest, werden Wartung und Upgrade der Maschine für Dich erledigt. Sie können Workflows direkt auf der virtuellen Maschine oder in einem Docker-Container ausführen. +When you use a {% data variables.product.prodname_dotcom %}-hosted runner, machine maintenance and upgrades are taken care of for you. You can run workflows directly on the virtual machine or in a Docker container. -Du kannst in einem Workflow für jeden Job die Art des Runners festlegen. Jeder Job in einem Workflow wird in einer neuen Instanz der virtuellen Maschine ausgeführt. Alle Schritte des Jobs werden in derselben Instanz der virtuellen Maschine ausgeführt, sodass die Aktionen in diesem Job über das Dateisystem Informationen austauschen können. +You can specify the runner type for each job in a workflow. Each job in a workflow executes in a fresh instance of the virtual machine. All steps in the job execute in the same instance of the virtual machine, allowing the actions in that job to share information using the filesystem. {% data reusables.github-actions.runner-app-open-source %} -#### Cloud-Hosts für {% data variables.product.prodname_dotcom %}-gehostete Runner +#### Cloud hosts for {% data variables.product.prodname_dotcom %}-hosted runners -{% data variables.product.prodname_dotcom %} betreibt Linux- und Windows-Runner auf den virtuellen Maschinen nach Standard_DS2_v2 in Microsoft Azure, auf denen die Runner-Anwendung der {% data variables.product.prodname_actions %} installiert ist. Die Runner-Anwendung auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern ist eine Fork-Kopie des Azure-Pipelines-Agenten. Bei Azure werden eingehende ICMP-Pakete werden für alle virtuellen Maschinen blockiert, so dass die Befehle ping und traceroute möglicherweise nicht funktionieren. Weitere Informationen zu den Ressourcen der Standard_DS2_v2-Maschinen findest Du unter „[Serien Dv2 und DSv2](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)“ in der Dokumentation zu Microsoft Azure. +{% data variables.product.prodname_dotcom %} hosts Linux and Windows runners on Standard_DS2_v2 virtual machines in Microsoft Azure with the {% data variables.product.prodname_actions %} runner application installed. The {% data variables.product.prodname_dotcom %}-hosted runner application is a fork of the Azure Pipelines Agent. Inbound ICMP packets are blocked for all Azure virtual machines, so ping or traceroute commands might not work. For more information about the Standard_DS2_v2 machine resources, see "[Dv2 and DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" in the Microsoft Azure documentation. {% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud. -#### Administrative Rechte von {% data variables.product.prodname_dotcom %}-gehosteten Runnern +#### Administrative privileges of {% data variables.product.prodname_dotcom %}-hosted runners -Die virtuellen Maschinen unter Linux und macOS werden beide mit dem passwortlosen Befehl `sudo` ausgeführt. 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)“. +The Linux and macOS virtual machines both 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)." -Die virtuellen Windows-Maschinen sind so konfiguriert, dass sie als Administratoren laufen, wobei die Benutzerkonten-Steuerung (UAC) deaktiviert ist. For more information, see "[How User Account Control works](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)" in the Windows documentation. +Windows virtual machines are configured to run as administrators with User Account Control (UAC) disabled. For more information, see "[How User Account Control works](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)" in the Windows documentation. -### Unterstützte Runner und Hardwareressourcen +### Supported runners and hardware resources -Für jede virtuelle Maschine stehen die gleichen Hardware-Ressourcen zur Verfügung. -- CPU mit 2 Kernen -- 7 GB RAM-Speicher -- 14 GB SSD-Festplattenspeicher +Hardware specification for Windows and Linux virtual machines: +- 2-core CPU +- 7 GB of RAM memory +- 14 GB of SSD disk space + +Hardware specification for macOS virtual machines: +- 3-core CPU +- 14 GB of RAM memory +- 14 GB of SSD disk space {% data reusables.github-actions.supported-github-runners %} @@ -56,7 +61,7 @@ Workflow logs list the runner used to run a job. For more information, see "[Vie ### Supported software -The software tools included in {% data variables.product.prodname_dotcom %}-hosted runners are updated weekly. Die neueste Liste der mitgelieferten Werkzeuge für jedes Runner-Betriebssystem findest Du unter den folgenden Links: +The software tools included in {% data variables.product.prodname_dotcom %}-hosted runners are updated weekly. For the latest list of included tools for each runner operating system, see the links below: * [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md) * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md) @@ -69,17 +74,23 @@ The software tools included in {% data variables.product.prodname_dotcom %}-host {% data reusables.github-actions.ubuntu-runner-preview %} {% data reusables.github-actions.macos-runner-preview %} -{% data variables.product.prodname_dotcom %}-gehostete Runner enthalten zusätzlich zu den oben aufgeführten Paketen die standardmäßig integrierten Tools des Betriebssystems. Zum Beispiel beinhalten Ubuntu und macOS Läufer `grep`, `find`, und `which` neben anderen Standard-Tools. +{% data variables.product.prodname_dotcom %}-hosted runners include the operating system's default built-in tools, in addition to the packages listed in the above references. For example, Ubuntu and macOS runners include `grep`, `find`, and `which`, among other default tools. -Workflow logs include a link to the preinstalled tools on the runner. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." +Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will tell you the the preinstalled tools on the runner that ran the workflow. +![Installed software link](/assets/images/actions-runner-installed-software-link.png) +For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -Wenn Sie ein bestimmtes Tool anfordern möchten, öffnen Sie bitte einen Issue unter [actions/virtual-environments](https://github.com/actions/virtual-environments). +We recommend using actions to interact with the software installed on runners. This approach has several benefits: +- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters +- It ensures the tool versions used in your workflow will remain the same regardless of software updates + +If there is a tool that you'd like to request, please open an issue at [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners. ### IP addresses {% note %} -**Notiz:** Wenn Du eine Liste mit erlaubten IP-Adressen für Dein Organisations- oder Unternehmenskonto auf {% data variables.product.prodname_dotcom %} verwendest, kannst Du keine {% data variables.product.prodname_dotcom %}-gehosteten Runner verwenden, sondern benötigst stattdessen selbst-gehostete Runner. Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners)“. +**Note:** If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you cannot use {% data variables.product.prodname_dotcom %}-hosted runners and must instead use self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% endnote %} @@ -87,25 +98,25 @@ Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API . For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint. You can use this list of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources. -The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. +The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. ### File systems -{% data variables.product.prodname_dotcom %} führt Aktionen und Shell-Befehle in bestimmten Verzeichnissen auf der virtuellen Maschine aus. Die Dateipfade auf virtuellen Maschinen sind nicht statisch. Verwende die von {% data variables.product.prodname_dotcom %} bereitgestellten Umgebungsvariablen zum Erstellen von Dateipfaden für die Verzeichnisse `home`, `workspace`und `workflow`. +{% data variables.product.prodname_dotcom %} executes actions and shell commands in specific directories on the virtual machine. The file paths on virtual machines are not static. Use the environment variables {% data variables.product.prodname_dotcom %} provides to construct file paths for the `home`, `workspace`, and `workflow` directories. -| Verzeichnis | Umgebungsvariable | Beschreibung | -| --------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `home` | `HOME` | Enthält benutzerbezogene Daten. In diesem Verzeichnis können sich beispielsweise die Anmeldeinformation aus einem Anmeldeversuch befinden. | -| `workspace` | `GITHUB_WORKSPACE` | Aktionen und Shell-Befehle werden in diesem Verzeichnis ausgeführt. Eine Aktion kann den Inhalt dieses Verzeichnisses ändern, auf den dann nachfolgende Aktionen zugreifen können. | -| `workflow/event.json` | `GITHUB_EVENT_PATH` | Die `POST`-Nutzlast des Webhook-Ereignisses, das den Workflow ausgelöst hat. {% data variables.product.prodname_dotcom %} schreibt dies bei jeder ausgeführten Aktion neu, sodass der Dateiinhalt zwischen den Aktionen isoliert wird. | +| Directory | Environment variable | Description | +|-----------|----------------------|-------------| +| `home` | `HOME` | Contains user-related data. For example, this directory could contain credentials from a login attempt. | +| `workspace` | `GITHUB_WORKSPACE` | Actions and shell commands execute in this directory. An action can modify the contents of this directory, which subsequent actions can access. | +| `workflow/event.json` | `GITHUB_EVENT_PATH` | The `POST` payload of the webhook event that triggered the workflow. {% data variables.product.prodname_dotcom %} rewrites this each time an action executes to isolate file content between actions. -Eine Liste der von {% data variables.product.prodname_dotcom %} für jeden Workflow erstellten Umgebungsvariablen findest Du unter „[Umgebungsvariablen verwenden](/github/automating-your-workflow-with-github-actions/using-environment-variables)“. +For a list of the environment variables {% data variables.product.prodname_dotcom %} creates for each workflow, see "[Using environment variables](/github/automating-your-workflow-with-github-actions/using-environment-variables)." -#### Docker-Container-Dateisystem +#### Docker container filesystem -Für Aktionen, die in Docker-Containern ausgeführt werden, befinden sich statische Verzeichnisse im Pfad `/github`. Wir empfehlen jedoch dringend, die Standard-Umgebungsvariablen zu verwenden, um Dateipfade in Docker-Containern zu erstellen. +Actions that run in Docker containers have static directories under the `/github` path. However, we strongly recommend using the default environment variables to construct file paths in Docker containers. -In {% data variables.product.prodname_dotcom %} wird das Pfadpräfix `/github` reserviert, und es werden drei Verzeichnisse für Aktionen erstellt. +{% data variables.product.prodname_dotcom %} reserves the `/github` path prefix and creates three directories for actions. - `/github/home` - `/github/workspace` - {% data reusables.repositories.action-root-user-required %} @@ -113,7 +124,7 @@ In {% data variables.product.prodname_dotcom %} wird das Pfadpräfix `/github` r {% if currentVersion == "free-pro-team@latest" %} -### Weiterführende Informationen -- „[Abrechnung für {{ site.data.variables.product.prodname_actions }} verwalten](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)“ +### Further reading +- "[Managing billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)" {% endif %} diff --git a/translations/de-DE/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/de-DE/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index 4f1447b115..69c2b39ae1 100644 --- a/translations/de-DE/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/de-DE/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -73,7 +73,7 @@ If the server on which you are running {% endif %} #### Enabling code scanning for individual repositories -After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. The default {% data variables.product.prodname_code_scanning %} workflow uses the `on.push` event to trigger a code scan on every push to any branch containing the workflow file. +After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." ### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %} If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. diff --git a/translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index 751f9cec33..f4da7e19c8 100644 --- a/translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md +++ b/translations/de-DE/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md @@ -20,7 +20,7 @@ For encryption in transit, {% data variables.product.product_name %} uses Transp The key that you provide is stored in a hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages. -To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and delete your encryption key. Note that deleting your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation. +To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation. ### Adding or updating an encryption key @@ -48,24 +48,24 @@ Your 2048 bit RSA private key should be in PEM format, for example in a file cal curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` -### Deleting your encryption key +### Disabling your encryption key -To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by deleting your encryption key. +To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled. -To unfreeze your enterprise after you've deleted your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)." - -1. To delete your key and disable encryption at rest, use the `DELETE /enterprise/encryption` endpoint. +1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently. ```shell curl -X DELETE http(s)://hostname/api/v3/enterprise/encryption ``` -2. Optionally, check the status of the delete operation. +2. Optionally, check the status of the delete operation. It takes approximately ten minutes to disable encryption at rest. ```shell curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` +To unfreeze your enterprise after you've disabled your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)." + ### Weiterführende Informationen - "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation diff --git a/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md index ad24cbb741..ab93dfea0c 100644 --- a/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/de-DE/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -29,6 +29,26 @@ versions: {% endnote %} +{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %} + +### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later + +Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table. + +| Benutzerlizenzen | vCPUs | Arbeitsspeicher | Attached-Storage | Root-Storage | +|:---------------------------------------------------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:| +| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen | **4**
_Up from 2_ | **32 GB**
_Up from 16 GB_ | **150 GB**
_Up from 100 GB_ | 200 GB | +| 10–3000 | **8**
_Up from 4_ | **48 GB**
_Up from 32 GB_ | **300 GB**
_Up from 250 GB_ | 200 GB | +| 3000–5000 | **12**
_Up from 8_ | 64 GB | 500 GB | 200 GB | +| 5000–8000 | **16**
_Up from 12_ | 96 GB | 750 GB | 200 GB | +| 8000–10000+ | **20**
_Up from 16_ | **160 GB**
_Up from 128 GB_ | 1000 GB | 200 GB | + +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% endif %} + ### Snapshot erstellen Ein Snapshot ist ein Checkpoint einer virtuellen Maschine (VM) zu einem bestimmten Zeitpunkt. Es wird dringend empfohlen, ein Snapshot zu erstellen, bevor Sie Ihre virtuelle Maschine upgraden, damit Sie bei einem Fehlschlagen eines Upgrades Ihre VM auf den Snapshot zurücksetzen können. Wenn Sie ein Upgrade auf eine neue Feature-Veröffentlichung durchführen, müssen Sie einen VM-Snapshot erstellen. Wenn Sie ein Upgrade auf eine Patch-Veröffentlichung durchführen, können Sie die vorhandene Daten-Disk anhängen. diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md index 65174fa7d8..3daa2b042f 100644 --- a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -9,13 +9,7 @@ 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-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} @@ -23,11 +17,33 @@ versions: This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies. +{% endif %} + ### Review hardware considerations +{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %} + +{% note %} + +**Note**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. Weitere Informationen finden Sie unter „[Upgrade von {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)“. + +{% endnote %} + +{% endif %} + {% data reusables.actions.enterprise-hardware-considerations %} -{% endif %} +For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform. + +- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) +- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) +- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) +- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) +- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) +- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations) +- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations) + +{% data reusables.enterprise_installation.about-adjusting-resources %} ### External storage requirements @@ -55,7 +71,7 @@ To enable {% data variables.product.prodname_actions %} on {% data variables.pro ### Enabling {% data variables.product.prodname_actions %} -{% 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/). +{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." ### Weiterführende Informationen diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md index 39f4fa5cc2..b27f25ac99 100644 --- a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md +++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md @@ -8,40 +8,40 @@ versions: free-pro-team: '*' --- -### Repositorys klonen -Repositorys auf {% data variables.product.prodname_dotcom %} existieren als Remote-Repositorys. Du kannst öffentliche Repositorys klonen, die anderen Personen gehören. Du kannst Dein Repository klonen, um eine lokale Kopie auf Deinem Computer zu erstellen, und die beiden Speicherorte synchronisieren. +### About local repositories +Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer. + +You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. For more information, see "[Syncing your branch](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)." + +When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. Weitere Informationen findest Du unter „[Informationen zu Forks](/github/collaborating-with-issues-and-pull-requests/about-forks)“. + +When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)". Darüber hinaus kannst Du ein Repository direkt über {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} klonen. Weitere Informationen findest Du unter „[Ein Repository von {% data variables.product.prodname_dotcom %} in {% data variables.product.prodname_desktop %} klonen](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)“. -{% mac %} +### Ein Repository klonen {% data reusables.desktop.choose-clone-repository %} - ![Menüoption zum Klonen in der Mac-App](/assets/images/help/desktop/clone-file-menu-mac.png) {% data reusables.desktop.cloning-location-tab %} - ![Standort-Registerkarten im Menü „Clone a repository“ (Repository klonen)](/assets/images/help/desktop/choose-repository-location-mac.png) {% data reusables.desktop.cloning-repository-list %} - ![Repository-Liste klonen](/assets/images/help/desktop/clone-a-repository-list-mac.png) -4. Klicke auf **Choose...** (Auswählen), und navigiere mithilfe des Finder-Fensters zu einem lokalen Pfad, wo Du das Repository klonen möchtest. ![Die Schaltfläche „choose“ (Auswählen)](/assets/images/help/desktop/clone-choose-button-mac.png) -5. Klicke auf **Clone** (Klonen). ![Die Schaltfläche „clone“ (Klonen)](/assets/images/help/desktop/clone-button-mac.png) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} -{% endmac %} - -{% windows %} +### Repository forken +If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork. {% data reusables.desktop.choose-clone-repository %} - ![Menüoption zum Klonen in der Windows-App](/assets/images/help/desktop/clone-file-menu-windows.png) {% data reusables.desktop.cloning-location-tab %} - ![Standort-Registerkarten im Menü „Clone a repository“ (Repository klonen)](/assets/images/help/desktop/choose-repository-location-win.png) {% data reusables.desktop.cloning-repository-list %} - ![Repository-Liste klonen](/assets/images/help/desktop/clone-a-repository-list-win.png) -4. Klicke auf **Choose...** (Auswählen), und navigiere mithilfe des Windows-Explorers zu einem lokalen Pfad, wohin Du das Repository klonen möchtest. ![Die Schaltfläche „choose“ (Auswählen)](/assets/images/help/desktop/clone-choose-button-win.png) -5. Klicke auf **Clone** (Klonen). ![Die Schaltfläche „clone“ (Klonen)](/assets/images/help/desktop/clone-button-win.png) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} +{% data reusables.desktop.fork-type-prompt %} -{% endwindows %} +### Managing fork behavior +You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}. -### Repositorys per Fork kopieren -Um zu einem Projekt beizutragen, in dem Du keinen Schreibzugriff hast, kannst Du mit {% data variables.product.prodname_desktop %} das Repository per Fork kopieren. Änderungen an Deinem Fork wirken sich nicht auf das ursprüngliche Repository aus. Du kannst per Commit Änderungen in deinen Fork übernehmen und dann in dem ursprünglichen Repository einen Pull-Request mit deinen vorgeschlagenen Änderungen öffnen. Weitere Informationen findest Du unter „[Informationen zu Forks](/github/collaborating-with-issues-and-pull-requests/about-forks)“. +{% data reusables.desktop.open-repository-settings %} +{% data reusables.desktop.select-fork-behavior %} -1. Wenn Du ein Repository geklont hast, in dem Du keinen Schreibzugriff hast, und dann versuchst, Änderungen per Commit zu übertragen, warnt {% data variables.product.prodname_desktop %}: „‚You don't have write access to **REPOSITORY**‘ (Du hast keinen Schreibzugriff auf **REPOSITORY**. ‚Click **create a fork**‘ (Klicke **Fork erstellen**).“ ![Einen Fork-Link erstellen](/assets/images/help/desktop/create-a-fork.png) -3. Klicke „**Fork this repository“ (Dieses Repository per Fork kopieren)**. ![Schaltfläche, um dieses Repo per Fork kopieren](/assets/images/help/desktop/fork-this-repo-button.png) -4. Um Deinen Fork auf {% data variables.product.prodname_dotcom %} zu sehen, klickst Du in der oberen rechten Ecke von {% data variables.product.prodname_dotcom %} auf Dein Profilbild und dann auf „**Your Repositories“ (Deine Repositorys)**. ![Link zu Deinen Repositorys](/assets/images/help/profile/your-repositories.png) +### Weiterführende Informationen +- [Informationen zu Remote-Repositorys](/github/using-git/about-remote-repositories) diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 9b1d2bb3cd..14dfc25597 100644 --- a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -9,7 +9,7 @@ versions: ### Informationen zu „Tags“ (Schlagworten) in {% data variables.product.prodname_desktop %} -{% data variables.product.prodname_desktop %} ermöglicht Dir, kommentierte Tags zu erstellen. Du kannst ein Tag verwenden, um einen einzelnen Punkt im Verlauf Deines Repositorys zu markieren, einschließlich einer Versionsnummer für eine Freigabe („Release“). Weitere Informationen zu Release-Tags findest Du unter „[Informationen zu Releases](/github/administering-a-repository/about-releases)“. +{% data variables.product.prodname_desktop %} ermöglicht Dir, kommentierte Tags zu erstellen. Tags are associated with commits, so you can use a tag to mark an individual point in your repository's history, including a version number for a release. Weitere Informationen zu Release-Tags findest Du unter „[Informationen zu Releases](/github/administering-a-repository/about-releases)“. {% data reusables.desktop.tags-push-with-commits %} @@ -44,3 +44,7 @@ versions: {% data reusables.desktop.history-tab %} {% data reusables.desktop.delete-tag %} + +### Weiterführende Informationen + +- "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation diff --git a/translations/de-DE/content/developers/apps/activating-beta-features-for-apps.md b/translations/de-DE/content/developers/apps/activating-beta-features-for-apps.md index f349501d5f..25c83f6d3f 100644 --- a/translations/de-DE/content/developers/apps/activating-beta-features-for-apps.md +++ b/translations/de-DE/content/developers/apps/activating-beta-features-for-apps.md @@ -3,6 +3,8 @@ title: Activating beta features for apps intro: 'You can test new app features released in public beta for your {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s.' versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% warning %} diff --git a/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md b/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md index 8305fed871..05a771d379 100644 --- a/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md @@ -110,7 +110,7 @@ The example above uses the maximum expiration time of 10 minutes, after which th ```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" + "documentation_url": "{% data variables.product.doc_url_pre %}" } ``` diff --git a/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 33c4c3b441..1adc4aad91 100644 --- a/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/de-DE/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### Einführung -This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. +This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Durch häufige Code-Aktualisierungen lassen sich zudem Änderungen von verschiedenen Mitgliedern eines Software-Entwicklungsteams leichter zusammenführen. Dies bedeutet einen erheblichen Vorteil für die Entwickler, die sich damit stärker auf das Schreiben des Codes konzentrieren können, statt Fehler debuggen oder Mergekonflikte beheben zu müssen. 🙌 @@ -49,7 +49,7 @@ To get an idea of what your Checks API CI server will do when you've completed t ### Vorrausetzungen -Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details. +Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details. You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app. @@ -203,7 +203,7 @@ Great! You've told GitHub to create a check run. You can see the check run statu ### Schritt 1.4. Updating a check run -When your `create_check_run` method runs, it asks GitHub to create a new check run. When Github finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check. +When your `create_check_run` method runs, it asks GitHub to create a new check run. When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check. You'll want to update your event handler to look for the `created` action. While you're updating the event handler, you can add a conditional for the `rerequested` action. When someone re-runs a single test on GitHub by clicking the "Re-run" button, GitHub sends the `rerequested` check run event to your app. When a check run is `rerequested`, you'll want to start the process all over and create a new check run. diff --git a/translations/de-DE/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/de-DE/content/developers/apps/migrating-oauth-apps-to-github-apps.md index 2c83c9cdbe..4c17351893 100644 --- a/translations/de-DE/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/de-DE/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -52,7 +52,7 @@ GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/under #### Register a new GitHub App -Once you've decided to make the switch to Github Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). +Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). #### Determine the permissions your app requires @@ -62,7 +62,7 @@ In your GitHub App's settings, you can specify whether your app needs `No Access #### Subscribe to webhooks -After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a Github App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. +After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. #### Understand the different methods of authentication diff --git a/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md index 3fb1433214..f85f2cf1ea 100644 --- a/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/de-DE/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,7 +42,7 @@ This callback request will send you a new access token and a new refresh token. { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" diff --git a/translations/de-DE/content/developers/apps/suspending-a-github-app-installation.md b/translations/de-DE/content/developers/apps/suspending-a-github-app-installation.md index bccc484a16..86da72d047 100644 --- a/translations/de-DE/content/developers/apps/suspending-a-github-app-installation.md +++ b/translations/de-DE/content/developers/apps/suspending-a-github-app-installation.md @@ -5,6 +5,8 @@ redirect_from: - /apps/managing-github-apps/suspending-a-github-app-installation versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% note %} diff --git a/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index 0b34ca2176..7bade46d0b 100644 --- a/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -14,7 +14,7 @@ versions: {% warning %} -If you offer a GitHub App in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate OAuth App to support this flow. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. +If you offer a {% data variables.product.prodname_github_app %} in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate {% data variables.product.prodname_oauth_app %} to support this flow. See "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endwarning %} @@ -24,7 +24,7 @@ Before a customer purchases your {% data variables.product.prodname_marketplace The customer completes the purchase by clicking **Complete order and begin installation**. -GitHub then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. +{% data variables.product.product_name %} then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. Read the `effective_date` and `marketplace_purchase` object from the `marketplace_purchase` webhook to determine which plan the customer purchased, when the billing cycle starts, and when the next billing cycle begins. @@ -34,27 +34,27 @@ See "[{% data variables.product.prodname_marketplace %} webhook events](/marketp ### Schritt 2. Installation -If your app is a GitHub App, GitHub prompts the customer to select which repositories the app can access when they purchase it. GitHub then installs the app on the account the customer selected and grants access to the selected repositories. +If your app is a {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} prompts the customer to select which repositories the app can access when they purchase it. {% data variables.product.product_name %} then installs the app on the account the customer selected and grants access to the selected repositories. -At this point, if you specified a **Setup URL** in your GitHub App settings, Github will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your GitHub App. +At this point, if you specified a **Setup URL** in your {% data variables.product.prodname_github_app %} settings, {% data variables.product.product_name %} will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your {% data variables.product.prodname_github_app %}. {% note %} -**Note:** The **Setup URL** is described as optional in GitHub App settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. +**Note:** The **Setup URL** is described as optional in {% data variables.product.prodname_github_app %} settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. {% endnote %} -If your app is an OAuth App, GitHub does not install it anywhere. Instead, GitHub redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). +If your app is an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} does not install it anywhere. Instead, {% data variables.product.product_name %} redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). -When a customer purchases an OAuth App, GitHub redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. +When a customer purchases an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. ### Schritt 3. Autorisierung When a customer purchases your app, you must send the customer through the OAuth authorization flow: -* If your app is a GitHub App, begin the authorization flow as soon as GitHub redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +* If your app is a {% data variables.product.prodname_github_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -* If your app is an OAuth App, begin the authorization flow as soon as GitHub redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/)." +* If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)." For either type of app, the first step is to redirect the customer to https://github.com/login/oauth/authorize. diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md index b33557b66e..dee57f6b73 100644 --- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -16,7 +16,7 @@ Repl.it is an online integrated development environment (IDE) that supports mult The first time the student clicks the button to visit Repl.it, the student must sign into Repl.it with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on Repl.it. -For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/misc/quick-start#the-repl-environment). +For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/repls/quick-start#the-repl-environment). For group assignments, students can use Repl.it Multiplayer to work collaboratively. For more information, see the [Repl.it Multiplayer](https://repl.it/site/multiplayer) website. diff --git a/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md index e53db4553c..47b667dc5c 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -3,6 +3,7 @@ title: About Dependabot version updates intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the packages you use updated to the latest versions.' redirect_from: - /github/administering-a-repository/about-dependabot + - /github/administering-a-repository/about-github-dependabot - /github/administering-a-repository/about-github-dependabot-version-updates versions: free-pro-team: '*' @@ -14,9 +15,9 @@ versions: {% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on. -You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file in to your repository. The configuration file specifies the location of the manifest, or other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository, rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary. +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary. -When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to directly replace the outdated dependency with the new version. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)." +When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)." If you enable security updates, {% data variables.product.prodname_dependabot %} also raises pull requests to update vulnerable dependencies. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." diff --git a/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md b/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md index d27a13c8e0..da31381068 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/de-DE/content/github/administering-a-repository/about-protected-branches.md @@ -82,13 +82,13 @@ After enabling required status checks, all required status checks must pass befo {% endnote %} -Du kannst die erforderlichen Statusprüfungen entweder als "loose" (locker) oder als "strict" (streng) einrichten. The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging. +Du kannst die erforderlichen Statusprüfungen entweder als "loose" (locker) oder als "strict" (streng) einrichten. Die Art der erforderlichen Statuschecks bestimmt, ob Dein Branch vor dem Zusammenführen auf dem aktuellen Stand mit dem Basisbranch sein muss. -| Art des erforderlichen Statuschecks | Einstellung | Merge-Anforderungen | Erwägungen | -| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Streng** | Das Kontrollkästchen **Require branches to be up-to-date before merging** (Aktualität der Branches vor dem Zusammenführen erzwingen) ist aktiviert. | Der Branch **muss** vor dem Zusammenführen auf dem Stand des Basisbranches sein. | Dies ist das Standardverhalten für erforderliche Statuschecks. Weitere Builds können erforderlich sein, da Du den Head-Branch auf den neuesten Stand bringen musst, nachdem andere Mitarbeiter Pull Requests in den geschützten Basisbranch überführt haben. | -| **Locker** | Das Kontrollkästchen **Require branches to be up-to-date before merging** (Aktualität der Branches vor dem Zusammenführen erzwingen) ist **nicht** aktiviert. | Der Branch muss vor dem Zusammenführen **nicht** auf dem Stand des Basisbranches sein. | Es sind weniger Builds erforderlich, da Du den Head-Branch nicht auf den neuesten Stand bringen musst, nachdem andere Mitarbeiter Pull Requests überführt haben. Statuschecks schlagen nach dem Zusammenführen Deines Branches möglicherweise fehl, wenn inkompatible Änderungen am Basisbranch vorliegen. | -| **Deaktiviert** | Das Kontrollkästchen **Require status checks to pass before merging** (Statuschecks müssen vor dem Zusammenführen bestanden werden) ist **deaktiviert**. | Für den Branch gelten keine Merge-Einschränkungen. | Wenn die erforderlichen Statuschecks nicht aktiviert sind, können Mitarbeiter den Branch unabhängig von seinem Stand gegenüber dem Basisbranch jederzeit zusammenführen. Die Wahrscheinlich inkompatibler Änderungen erhöht sich dadurch jedoch. | +| Art des erforderlichen Statuschecks | Einstellung | Merge-Anforderungen | Erwägungen | +| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Streng** | The **Require branches to be up to date before merging** checkbox is checked. | Der Branch **muss** vor dem Zusammenführen auf dem Stand des Basisbranches sein. | Dies ist das Standardverhalten für erforderliche Statuschecks. Weitere Builds können erforderlich sein, da Du den Head-Branch auf den neuesten Stand bringen musst, nachdem andere Mitarbeiter Pull Requests in den geschützten Basisbranch überführt haben. | +| **Locker** | The **Require branches to be up to date before merging** checkbox is **not** checked. | Der Branch muss vor dem Zusammenführen **nicht** auf dem Stand des Basisbranches sein. | Es sind weniger Builds erforderlich, da Du den Head-Branch nicht auf den neuesten Stand bringen musst, nachdem andere Mitarbeiter Pull Requests überführt haben. Statuschecks schlagen nach dem Zusammenführen Deines Branches möglicherweise fehl, wenn inkompatible Änderungen am Basisbranch vorliegen. | +| **Deaktiviert** | Das Kontrollkästchen **Require status checks to pass before merging** (Statuschecks müssen vor dem Zusammenführen bestanden werden) ist **deaktiviert**. | Für den Branch gelten keine Merge-Einschränkungen. | Wenn die erforderlichen Statuschecks nicht aktiviert sind, können Mitarbeiter den Branch unabhängig von seinem Stand gegenüber dem Basisbranch jederzeit zusammenführen. Die Wahrscheinlich inkompatibler Änderungen erhöht sich dadurch jedoch. | For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." diff --git a/translations/de-DE/content/github/administering-a-repository/about-securing-your-repository.md b/translations/de-DE/content/github/administering-a-repository/about-securing-your-repository.md index abb3eb130d..ae82505b95 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/about-securing-your-repository.md @@ -14,6 +14,8 @@ The first step to securing a repository is to set up who can see and modify your {% data variables.product.prodname_dotcom %} has a growing set of security features that help you keep your code secure. You can find these on the **Security** tab for your repository. +#### Available for all repositories + {% if currentVersion == "free-pro-team@latest" %} - **Security policy** @@ -43,15 +45,23 @@ Use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %} + +These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} + - **{% data variables.product.prodname_code_scanning_capc %} alerts** Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." - **Detected secrets** -View any secrets that - {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." - {% endif %} + {% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else if %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +- **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 "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +{% endif %} ### Exploring dependencies {% data variables.product.prodname_dotcom %}'s dependency graph allows you to explore: @@ -59,6 +69,6 @@ View any secrets that * Ecosystems and packages that your repository depends on * Repositories and packages that depend on your repository -You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. +You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. {% if currentVersion == "free-pro-team@latest" %}Enabling the dependency graph also enables {% data variables.product.prodname_dotcom %} to run dependency reviews of pull requests.{% endif %} You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." diff --git a/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md index 370e25d035..025f235d91 100644 --- a/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md +++ b/translations/de-DE/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -27,13 +27,13 @@ versions: {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) 5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) 6. When you enable {% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. - ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png) + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} 4. To the right of " {% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) diff --git a/translations/de-DE/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index e19203c066..5ff425d08d 100644 --- a/translations/de-DE/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -4,13 +4,12 @@ intro: "You can allow or disallow auto-merge for pull requests in your repositor product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' permissions: People with maintainer permissions can manage auto-merge for pull requests in a repository. --- -{% data reusables.pull_requests.auto-merge-release-phase %} - If you allow auto-merge for pull requests in your repository, people can configure individual pull requests in the repository to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Under "Merge button", select or deselect **Allow auto-merge**. ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) \ No newline at end of file +1. Under "Merge button", select or deselect **Allow auto-merge**. ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) diff --git a/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index 25c042da2d..bfbac951b1 100644 --- a/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -33,10 +33,15 @@ You can manage the security and analysis features for your {% if currentVersion {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} 4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. -{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} +**Note:** If you disable + + {% data variables.product.prodname_GH_advanced_security %}, both {% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail. + {% endnote %} + + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) {% endif %} diff --git a/translations/de-DE/content/github/administering-a-repository/securing-your-repository.md b/translations/de-DE/content/github/administering-a-repository/securing-your-repository.md index b193526260..f63e4cb821 100644 --- a/translations/de-DE/content/github/administering-a-repository/securing-your-repository.md +++ b/translations/de-DE/content/github/administering-a-repository/securing-your-repository.md @@ -6,5 +6,6 @@ redirect_from: - /articles/securing-your-repository versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- diff --git a/translations/de-DE/content/github/administering-a-repository/setting-repository-visibility.md b/translations/de-DE/content/github/administering-a-repository/setting-repository-visibility.md index eb895dec72..88295601db 100644 --- a/translations/de-DE/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/de-DE/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,7 +24,7 @@ We recommend reviewing the following caveats before you change the visibility of * If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} * If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %} * Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} * {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %} diff --git a/translations/de-DE/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/de-DE/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md index 49802b09f4..644d44200d 100644 --- a/translations/de-DE/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md +++ b/translations/de-DE/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md @@ -33,14 +33,18 @@ Wenn Sie einen GPG-Schlüssel verwenden, der mit Ihrer Beitragenderidentität un Comment: GitHub key Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? ``` -7. Gib `O` ein, um Deine Auswahl zu speichern. +7. Enter `O` to confirm your selections. 8. Gib die Passphrase Deines Schlüssels ein. -9. Gib `gpg --armor --export GPG key ID` ein. Setze dabei die gewünschte GPG-Schlüssel-ID ein. Im folgenden Beispiel ist die GPG-Schlüssel-ID `3AA5C34371567BD2`: +9. Enter `gpg> save` to save the changes + ```shell + $ gpg> save + ``` +10. Geben Sie `gpg --armor --export GPG key ID` ein. Setzen Sie dabei die gewünschte GPG-Schlüssel-ID ein. Im folgenden Beispiel ist die GPG-Schlüssel-ID `3AA5C34371567BD2`: ```shell $ gpg --armor --export 3AA5C34371567BD2 # Gibt den GPG Schluessel im ASCII armor format aus ``` -10. Lade den GPG-Schlüssel hoch, indem Du ihn [zu Deinem GitHub-Konto hinzufügst](/articles/adding-a-new-gpg-key-to-your-github-account). +11. Laden Sie den GPG-Schlüssel hoch, indem Sie ihn [zu Ihrem GitHub-Konto hinzufügen](/articles/adding-a-new-gpg-key-to-your-github-account). ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index c67c7ba7a0..1d586c7e2d 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -4,10 +4,9 @@ intro: 'You can increase development velocity by enabling auto-merge for a pull product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' --- -{% data reusables.pull_requests.auto-merge-release-phase %} - ### About auto-merge If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks. diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index 6d79251790..61da6f4bb7 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -9,7 +9,6 @@ versions: github-ae: '*' --- - ### Informationen zum Zusammenführen von Pull Requests Mit einem Pull Request schlägst Du vor, dass Änderungen, die Du an einem Head-Branch gemacht hast, in einen Basis-Branch zusammengeführt werden sollten. Standardmäßig kann jeder Pull Request jederzeit zusammengeführt werden, es sei denn, der Head-Branch steht in Konflikt mit dem Basisbranch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches).“ diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index 48d5d43d9c..1b46db9ffb 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -23,7 +23,7 @@ Wenn ein Benutzer mit Administrator- oder Inhaberberechtigungen die erforderlich {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If a team has enabled code review assignments, the individual approvals won't satisfy the requirement for code owner approval in a protected branch. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Wenn eine Datei einen Codeinhaber hat, kannst Du sehen, wer der Codeinhaber ist, bevor Du einen Pull Request öffnest. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}. diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index 783872b8ad..9684696ef4 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -12,25 +12,26 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### Informationen zu {% data variables.product.prodname_code_scanning %} +### About {% data variables.product.prodname_code_scanning %} -With {% data variables.product.prodname_code_scanning %}, developers can quickly and automatically analyze the code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. +{% 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. Nachdem Du den Code korrigiert hast, der die Meldung ausgelöst hat, schließt {% data variables.product.prodname_dotcom %} die Meldung. 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)." +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 webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see +"[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." -To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)." +To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." -### Informationen zu {% data variables.product.prodname_codeql %} +### About {% data variables.product.prodname_codeql %} -{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}. {% 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. +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. -For more information about API endpoints for {% data variables.product.prodname_code_scanning %}, see "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)." +{% 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 %} @@ -38,9 +39,9 @@ You can view and contribute to the queries for {% data variables.product.prodnam {% if currentVersion == "free-pro-team@latest" %} -### Informationen zur Abrechnung für {% data variables.product.prodname_code_scanning %} +### 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 %}. Weitere Informationen findest Du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions).“ +{% 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 %} @@ -52,7 +53,7 @@ You can view and contribute to the queries for {% data variables.product.prodnam {% data reusables.code-scanning.get-started-uploading-third-party-data %} -### Weiterführende Informationen +### Further reading {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index d2288c0735..c1cac87058 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -134,19 +134,22 @@ Attempts to build the code for the compiled languages C/C++, C#, and Java. For t Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_location %}. -| Flag | Erforderlich | Input value | -| -------------------------------- |:------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--repository` | ✓ | 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. | +| Flag | Erforderlich | Input value | +| ---------------------------------- |:------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `--repository` | ✓ | 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. | +| `--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. | +| `--threads` | | Number of threads to use when running queries. The default is to use all available cores. | +| `--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. | #### `hochladen` diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md index 2b8fc4d674..6e93eaa1f1 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md @@ -17,7 +17,7 @@ versions: ### About the {% data variables.product.prodname_codeql_workflow %} and compiled languages -You enable {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. The default {% data variables.product.prodname_code_scanning %} workflow uses the `on.push` event to trigger a code scan on every push to any branch containing the workflow file. +You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} For general information about configuring diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md index dbbd09cc1c..7d4bcdc4ad 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md @@ -14,7 +14,7 @@ versions: {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %} {% link_in_list /about-code-scanning %} {% link_in_list /triaging-code-scanning-alerts-in-pull-requests %} - {% link_in_list /enabling-code-scanning %} + {% link_in_list /setting-up-code-scanning-for-a-repository %} {% link_in_list /managing-code-scanning-alerts-for-your-repository %} {% link_in_list /configuring-code-scanning %} {% link_in_list /configuring-the-codeql-workflow-for-compiled-languages %} diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 81c7f84190..6f310ccccc 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -16,7 +16,7 @@ redirect_from: ### About alerts from {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. The default {% data variables.product.prodname_code_scanning %} workflow uses the `on.push` event to trigger a code scan on every push to any branch containing the workflow file. +You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." @@ -28,7 +28,7 @@ Each alert highlights a problem with the code and the name of the tool that iden ![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) -If you enable {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information. +If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information. When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users. @@ -65,7 +65,7 @@ Closing an alert is a way to resolve an alert that you don't think needs to be f ### Dismissing or deleting alerts -There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have enabled a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have enabled {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab. +There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab. Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab. @@ -127,5 +127,5 @@ If a project has multiple alerts that you want to dismiss for the same reason, y ### Weiterführende Informationen - "[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)" -- "[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)" +- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" - "[About integration with {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)" diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 2d92e06f15..8a44d4a134 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -24,7 +24,7 @@ If you use a continuous integration or continuous delivery/deployment (CI/CD) sy {% 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)." +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 "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-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. diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index f4c782d9b7..caa60f99c8 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -97,7 +97,6 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr | `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). | -| `suppressions[].state` | **Optional.** When the `state` is set to `accepted`, {% data variables.product.prodname_code_scanning %} will update the state of the result to `Closed` on {% data variables.product.prodname_dotcom %}. | #### `location` object diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md new file mode 100644 index 0000000000..63230d683f --- /dev/null +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -0,0 +1,117 @@ +--- +title: Setting up code scanning for a repository +shortTitle: Setting up code scanning +intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.' +redirect_from: + - /github/managing-security-vulnerabilities/configuring-automated-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} + +### Options for setting up {% data variables.product.prodname_code_scanning %} + +You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to 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. Weitere Informationen findest Du unter „[ Über {% 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 %} + +### Setting up {% 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. Weitere Informationen finden Sie unter „[Informationen zur Abrechnung für {% 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 %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/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) +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. As a result, {% data variables.product.prodname_code_scanning %} will now commence. + +### 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. 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. + +### 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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. + + ![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 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. + +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, 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 %}. + +### Nächste Schritte: + +After setting up {% 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 set up {% 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. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/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/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index ff5dc52758..2ec882d748 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -15,7 +15,7 @@ versions: 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, 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 notices and the check succeeds. If your pull request targets a protected branch that has been enabled for {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“ +If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, 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 notices and the check succeeds. 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 you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“ ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 27416ac984..043231d190 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -75,7 +75,7 @@ When ### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% 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 %} +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](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} By default, we notify people with admin permissions in the affected repositories about new @@ -89,6 +89,11 @@ Standardmäßig senden wir Sicherheitsmeldungen an Personen mit Administratorrec {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} 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" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +You can also see all the +{% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in 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#viewing-your-vulnerable-repositories)." +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/de-DE/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md index 53f4ca138b..7db467beed 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -24,7 +24,7 @@ Es gibt vier mögliche Schweregrade, die im [Common Vulnerability Scoring System - Hoch - Kritisch -The {% data variables.product.prodname_advisory_database %} uses CVSS version 3.0 standards and the CVSS levels described above. {% data variables.product.product_name %} doesn't publish CVSS scores. +The {% data variables.product.prodname_advisory_database %} uses CVSS version 3.0 standards and the CVSS levels described above. {% data reusables.repositories.github-security-lab %} @@ -41,24 +41,39 @@ Die Datenbank ist auch über die GraphQL-API zugänglich. For more information, {% endnote %} ### Durchsuche die {% data variables.product.prodname_advisory_database %} -Du kannst die Datenbank durchsuchen und mit den Qualifizierern Deine Suche auf Hinweise einschränken, die an einem bestimmten Datum, in einem bestimmten Ökosystem oder in einer bestimmten Bibliothek erstellt wurden. + +You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifizierer | Beispiel | -| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ecosystem:ÖKOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) wird nur Hinweise zeigen, die NPM Pakete betreffen. | -| `severity:STUFE` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) wird nur Hinweise mit einer Schweregrad von Hoch zeigen. | -| `affects:BIBLIOTHEK` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) wird nur Hinweise anzeigen, die die lodash Bibliothek betreffen. | -| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) sortiert nach ältesten Hinweisen zuerst. | -| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) sortiert nach neuesten Hinweisen zuerst. | -| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) sortiert nach den ältesten Aktualisierungen von Hinweisen zuerst. | -| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) sortiert nach den neuesten Aktualisierungen von Hinweisen zuerst. | -| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) zeigt nur zurückgezogene Hinweise. | -| `created:YYYY-MM-DD` | [**created:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2019-10-31) zeigt nur Hinweise, die an diesem Datum erstellt wurden. | -| `updated:YYYY-MM-DD` | [**updated:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2019-10-31) zeigt nur Hinweise, die an diesem Datum aktualisiert wurden. | +| Qualifizierer | Beispiel | +| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `GHSA-ID` | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | +| `CVE-ID` | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | +| `ecosystem:ÖKOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) wird nur Hinweise zeigen, die NPM Pakete betreffen. | +| `severity:STUFE` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) wird nur Hinweise mit einer Schweregrad von Hoch zeigen. | +| `affects:BIBLIOTHEK` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) wird nur Hinweise anzeigen, die die lodash Bibliothek betreffen. | +| `cwe:ID` | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | +| `credit:USERNAME` | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | +| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) sortiert nach ältesten Hinweisen zuerst. | +| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) sortiert nach neuesten Hinweisen zuerst. | +| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) sortiert nach den ältesten Aktualisierungen von Hinweisen zuerst. | +| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) sortiert nach den neuesten Aktualisierungen von Hinweisen zuerst. | +| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) zeigt nur zurückgezogene Hinweise. | +| `created:YYYY-MM-DD` | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) zeigt nur Hinweise, die an diesem Datum erstellt wurden. | +| `updated:YYYY-MM-DD` | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) zeigt nur Hinweise, die an diesem Datum aktualisiert wurden. | + +### Viewing your vulnerable repositories + +For any vulnerability in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories have a {% data variables.product.prodname_dependabot %} alert for that vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)." | + +1. Navigiere zu „https://github.com/advisories“. +2. Click an advisory. +3. At the top of the advisory page, click **Dependabot alerts**. ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png) +4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) +5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name. ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index fc6c2bb2ac..c6bbdd3788 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -12,6 +12,8 @@ versions: {% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." +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 %} usage beyond the amounts including with your account. 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)." + Minuten werden jeden Monat zurückgesetzt, während Speichernutzung dies nicht tut. | Produkt | Speicher | Minuten (pro Monat) | diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 32b5054987..a5b59f2335 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.package_registry.container-registry-beta-billing-note %} +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_registry %} usage beyond the amounts including with your account. 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)." + Die Datenübertragung wird jeden Monat zurückgesetzt, während Speichernutzung dies nicht tut. | Produkt | Speicher | Datenübertragung (pro Monat) | diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index cd6248a3dc..e51667fa66 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} 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)." +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 %} usage beyond the amounts including with your account. 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)." + As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. Wenn Dein Unternehmen beispielsweise {% data variables.product.prodname_team %} verwendet, keine Überschreitungen zulässt, und Workflow-Artefakte erstellt, die Deinen Speicherverbrauch für den Monat von 1,9 GB auf 2,1 GB erhöht, wirst Du leicht mehr Speicher als die 2 GB nutzen, die Dein Produkt enthält. Because you have not enabled overages, your next attempt to create a workflow artifact will fail. Du wirst keine Rechnung für die Überschreitung um 0,1 GB für diesen Monat erhalten. However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue. diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index d6cadae2cc..bad21cd3b9 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} 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)." +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_registry %} usage beyond the amounts including with your account. 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)." + As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. Wenn Dein Unternehmen beispielsweise {% data variables.product.prodname_team %} verwendet, keine Überschreitungen zulässt, und Workflow-Artefakte erstellt, die Deinen Speicherverbrauch für den Monat von 1,9 GB auf 2,1 GB erhöht, wird die Veröffentlichung leicht mehr Speicher als die 2 GB nutzen, die Dein Produkt enthält. Da Du keine Überschreitungen zugelassen hast, wird Dein nächster Versuch, eine Version des Pakets zu veröffentlichen, fehlschlagen. Du wirst keine Rechnung für die Überschreitung um 0,1 GB für diesen Monat erhalten. However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue. diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 7c807260e6..8a3360743f 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -23,8 +23,13 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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. +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. +{% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@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.{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) {% endif %} @@ -42,24 +47,21 @@ You can enable or disable features for all repositories. {% if currentVersion == 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)." 1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) {% endif %} 2. Optionally, enable the feature by default for new repositories in your organization. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) {% endif %} -1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. - {% if currentVersion == "free-pro-team@latest" %} +3. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) {% endif %} @@ -68,10 +70,9 @@ You can enable or disable features for all repositories. {% if currentVersion == 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)." 1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories {% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![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 %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) {% endif %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 7a3a3f3ca8..254470fde0 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -70,7 +70,7 @@ Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben {% 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** |{% if currentVersion == "free-pro-team@latest" %} +| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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** | @@ -150,8 +150,8 @@ In this section, you can find the repository permission levels required for secu | Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | | [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/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** | -| [Sicherheitshinweise](/github/managing-security-vulnerabilities/about-github-security-advisories) erstellen | | | | | **X** | -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| [Sicherheitshinweise](/github/managing-security-vulnerabilities/about-github-security-advisories) erstellen | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | [Aktivieren des Abhängigkeitsdiagramms](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) für ein privates Repository | | | | | **X** | | [View dependency reviews](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | [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** | diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md new file mode 100644 index 0000000000..ea9b3d4b19 --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md @@ -0,0 +1,40 @@ +--- +title: Connecting an Azure subscription to your enterprise +intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the included amounts for your enterprise.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise +versions: + free-pro-team: '*' +--- + +### About Azure subscriptions and {% data variables.product.product_name %} + +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 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) and "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." + +After you connect an Azure subscription, you can also manage your spending limit. For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)" and "[Managing your spending limit for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)." + +### Connecting your Azure subscription to your enterprise account + +To connect your Azure subscription, you must have owner permissions to the subscription. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Payment Information", click **Add Azure Subscription**. +1. To sign in to your Microsoft account, follow the prompts. +1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**. +1. Under "Select a subscription", select the Azure Subscription ID that you want to connect to your enterprise. +1. Click **Connect**. + +### Disconnecting your Azure subscription from your enterprise account + +After you disconnect your Azure subscription from your enterprise account, your usage can no longer exceed the amounts included with your plan. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. +1. Review the prompt, then click **Remove**. 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 1e48a76711..afe58b89e6 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 @@ -18,6 +18,7 @@ versions: {% link_in_list /about-enterprise-accounts %} {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %} {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %} + {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %} {% topic_link_in_list /managing-users-in-your-enterprise %} {% link_in_list /roles-in-an-enterprise %} {% link_in_list /inviting-people-to-manage-your-enterprise %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md index 4d57c2f3c8..e0b69f48a5 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md @@ -31,7 +31,7 @@ Enterprise owners have complete control over the enterprise and can take every a Keinen Zugriff haben Enterprise-Inhaber auf die Einstellungen und Inhalte der einzelnen Organisationen, es sei denn, sie sind auch Inhaber einer Organisation oder ihnen wird direkter Zugriff auf das Repository einer Organisation erteilt. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. -You can add as many enterprise owners as you'd like to your enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. +An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. ### Enterprise-Mitglieder @@ -52,7 +52,7 @@ Billing managers only have access to your enterprise's billing settings. Billing - Liste der Abrechnungsmanager anzeigen - Andere Abrechnungsmanager hinzufügen oder entfernen -Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Abrechnungsmanager müssen über ein persönliches Konto auf {% data variables.product.prodname_dotcom %} verfügen. +Billing managers will only consume a license if they are an owner or member of at least one organization within the enterprise. Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Abrechnungsmanager müssen über ein persönliches Konto auf {% data variables.product.prodname_dotcom %} verfügen. ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 4fe05845a6..7ad3370c10 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -15,6 +15,8 @@ versions: Enterprise-Konten sind derzeit für {% data variables.product.prodname_enterprise %}-Kunden verfügbar, die per Rechnung bezahlen. Die Abrechnung für alle Organisationen und {% data variables.product.prodname_ghe_server %}-Instanzen, die mit Deinem Enterprise-Konto verbunden sind, wird in eine einzige Rechnung für alle Deine bezahlten {% data variables.product.prodname_dotcom_the_website %}-Dienste zusammengefasst (inklusive bezahlte Lizenzen in Organisationen, {% data variables.large_files.product_name_long %}-Datenpakete und Abonnements für {% data variables.product.prodname_marketplace %}-Apps). +{% if currentVersion == "free-pro-team@latest" %}{% 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)."{% endif %} + For more information about managing billing managers, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." ### Abonnement und Nutzung für Dein Enterprise-Konto anzeigen diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index b4c0187e13..5bf30d3e16 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -50,7 +50,7 @@ Der Repository-Inhaber besitzt die vollständige Kontrolle über das Repository. | Codeinhaber für das Repository definieren | „[Informationen zu Codeinhabern](/github/creating-cloning-and-archiving-repositories/about-code-owners)“ | | Archive the repository | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | Sicherheitshinweise erstellen | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | -| Eine Sponsorenschaltfläche anzeigen | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" | +| Eine Sponsorenschaltfläche anzeigen | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} | Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %} ### Collaborator access for a repository owned by a user account diff --git a/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index 0b93f625bc..e31e997244 100644 --- a/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -25,8 +25,6 @@ Bevor Sie mit Jekyll eine {% data variables.product.prodname_pages %}-Website er {% 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 %} @@ -36,6 +34,8 @@ Bevor Sie mit Jekyll eine {% data variables.product.prodname_pages %}-Website er {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% data reusables.command_line.open_the_multi_os_terminal %} 2. Wenn Du noch keine lokale Kopie Deines Repositorys besitzt, navigiere zu dem Speicherort, an dem Du die Quelldateien Deiner Website speichern möchtest, und ersetze dabei _PARENT-FOLDER_ durch den Ordner, der den Ordner für Dein Repository enthalten soll. ```shell diff --git a/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site.md b/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site.md index 4bbeeb57d8..e03ab73157 100644 --- a/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site.md +++ b/translations/de-DE/content/github/working-with-github-pages/creating-a-github-pages-site.md @@ -20,8 +20,6 @@ versions: {% 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 %} @@ -33,6 +31,8 @@ versions: {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% data reusables.pages.navigate-site-repo %} {% data reusables.pages.decide-publishing-source %} 3. Wenn Deine ausgewählte Veröffentlichungsquelle bereits vorhanden ist, navigiere zu dieser Quelle. Wenn Deine ausgewählte Veröffentlichungsquelle nicht vorhanden ist, erstelle die Veröffentlichungsquelle. diff --git a/translations/de-DE/content/rest/overview/libraries.md b/translations/de-DE/content/rest/overview/libraries.md index 2d0f25d9c9..51935046da 100644 --- a/translations/de-DE/content/rest/overview/libraries.md +++ b/translations/de-DE/content/rest/overview/libraries.md @@ -57,7 +57,7 @@ Library name | Repository | |---|---| **NodeJS GitHub library**| [pksunkara/octo ### Julia -Library name | Repository | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl) +Library name | Repository | |---|---| **GitHub.jl**|[WestleyArgentum/GitHub.jl](https://github.com/WestleyArgentum/GitHub.jl) ### OCaml @@ -65,11 +65,11 @@ Library name | Repository | |---|---| **ocaml-github**|[mirage/ocaml-github](htt ### Perl -Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub) +Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub) ### PHP -Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI) +Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GitHubAPI](https://github.com/FlexyProject/GitHubAPI) ### Python diff --git a/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md b/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md index a3d2cc5f87..ce69babcca 100644 --- a/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md @@ -129,7 +129,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar > { > "message": "Bad credentials", -> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -141,7 +141,7 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f > 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" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -358,7 +358,7 @@ If you exceed the rate limit, an error response returns: > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#rate-limiting" > } ``` @@ -403,7 +403,7 @@ If your application triggers this rate limit, you'll receive an informative resp > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#abuse-rate-limits" > } ``` diff --git a/translations/de-DE/content/rest/reference/repos.md b/translations/de-DE/content/rest/reference/repos.md index f87011fdb5..4c3666846d 100644 --- a/translations/de-DE/content/rest/reference/repos.md +++ b/translations/de-DE/content/rest/reference/repos.md @@ -141,7 +141,7 @@ Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth- ### Inactive deployments -When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. +When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository to the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. You can communicate that a transient environment no longer exists by setting its `state` to `inactive`. Setting the `state` to `inactive` shows the deployment as `destroyed` in {% data variables.product.prodname_dotcom %} and removes access to it. diff --git a/translations/de-DE/data/reusables/actions/enterprise-beta.md b/translations/de-DE/data/reusables/actions/enterprise-beta.md index b10237e282..0c674122af 100644 --- a/translations/de-DE/data/reusables/actions/enterprise-beta.md +++ b/translations/de-DE/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,12 @@ {% if enterpriseServerVersions contains currentVersion 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 "[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)." +**Note:** {% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. The beta has ended. {% data variables.product.prodname_actions %} is now generally available in {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +
+ +- For more information about upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." +- For more information about configuring {% data variables.product.prodname_actions %} after you upgrade, see the [documentation for {% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server). {% endnote %} {% endif %} diff --git a/translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md b/translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md index ee9ba1dca8..3a9923ae8e 100644 --- a/translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md +++ b/translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md @@ -1,4 +1,4 @@ -* {% data reusables.actions.enterprise-hardware-considerations %} +* Review the hardware requirements for {% data variables.product.prodname_actions %}. 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#review-hardware-considerations)." * TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." {% note %} diff --git a/translations/de-DE/data/reusables/actions/enterprise-hardware-considerations.md b/translations/de-DE/data/reusables/actions/enterprise-hardware-considerations.md index 24c077bbae..98ac65f438 100644 --- a/translations/de-DE/data/reusables/actions/enterprise-hardware-considerations.md +++ b/translations/de-DE/data/reusables/actions/enterprise-hardware-considerations.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "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)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. +If you {% if currentVersion == "enterprise-server@2.22" %} configured the beta of{% else %} configure{% endif %} {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, we recommend that you provision additional CPU and memory resources. The additional resources you need to provision depend on the number of workflows your users run concurrently, and the overall levels of activity for your instance. diff --git a/translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md index 48f3c5a99a..733e8e8a97 100644 --- a/translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md +++ b/translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -1,7 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. This option controls access to all {% data variables.product.prodname_advanced_security %} features including {% if currentVersion == "free-pro-team@latest" %}dependency review,{% endif %} {% data variables.product.prodname_code_scanning %}, and {% data variables.product.prodname_secret_scanning %}. {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/code-scanning/enabling-options.md b/translations/de-DE/data/reusables/code-scanning/enabling-options.md index 3ef6731b26..bbbd1a7893 100644 --- a/translations/de-DE/data/reusables/code-scanning/enabling-options.md +++ b/translations/de-DE/data/reusables/code-scanning/enabling-options.md @@ -15,7 +15,7 @@ - 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"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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"). @@ -25,7 +25,7 @@ - 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 %}"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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 %}"). 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 3fd62db750..784d7b39aa 100644 --- a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md +++ b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md @@ -8,7 +8,7 @@ The following table shows, for each package manager: | -------------- | ---------------- | ------------------------- |:--------------------:|:---------:| | Bundler | `bundler` | v1 | | **✓** | | Cargo | `cargo` | v1 | **✓** | | -| Composer | `composer` | v1,v2 | **✓** | | +| Composer | `composer` | v1, v2 | **✓** | | | Docker | `docker` | v1 | **✓** | | | Elixir | `mix` | v1 | **✓** | | | Elm | `elm` | v0.18, v0.19 | **✓** | | @@ -17,7 +17,7 @@ The following table shows, for each package manager: | Go modules | `gomod` | v1 | **✓** | **✓** | | Gradle | `gradle` | see (A) below | **✓** | | | Maven | `maven` | see (B) below | **✓** | | -| npm | `npm` | v6 | **✓** | | +| npm | `npm` | v6, v7 | **✓** | | | NuGet | `nuget` | <= 4.8.
see (C) below | **✓** | | | pip | `pip` | v20 | | | | pipenv | `pip` | <= 2018.11.26 | | | diff --git a/translations/de-DE/data/reusables/desktop/choose-clone-repository.md b/translations/de-DE/data/reusables/desktop/choose-clone-repository.md index 8d0addc22d..c425d62300 100644 --- a/translations/de-DE/data/reusables/desktop/choose-clone-repository.md +++ b/translations/de-DE/data/reusables/desktop/choose-clone-repository.md @@ -1 +1,13 @@ 1. Klicke im Menü **File** (Datei) auf ** Clone repository** (Repository klonen). + + {% mac %} + + ![Menüoption zum Klonen in der Mac-App](/assets/images/help/desktop/clone-file-menu-mac.png) + + {% endmac %} + + {% windows %} + + ![Menüoption zum Klonen in der Windows-App](/assets/images/help/desktop/clone-file-menu-windows.png) + + {% endwindows %} diff --git a/translations/de-DE/data/reusables/desktop/choose-local-path.md b/translations/de-DE/data/reusables/desktop/choose-local-path.md new file mode 100644 index 0000000000..85ff7e2477 --- /dev/null +++ b/translations/de-DE/data/reusables/desktop/choose-local-path.md @@ -0,0 +1,13 @@ +1. Click **Choose...** and navigate to a local path where you want to clone the repository. + + {% mac %} + + ![Die Schaltfläche „choose“ (Auswählen)](/assets/images/help/desktop/clone-choose-button-mac.png) + + {% endmac %} + + {% windows %} + + ![Die Schaltfläche „choose“ (Auswählen)](/assets/images/help/desktop/clone-choose-button-win.png) + + {% endwindows %} diff --git a/translations/de-DE/data/reusables/desktop/click-clone.md b/translations/de-DE/data/reusables/desktop/click-clone.md new file mode 100644 index 0000000000..d3dcadb565 --- /dev/null +++ b/translations/de-DE/data/reusables/desktop/click-clone.md @@ -0,0 +1,14 @@ +1. Klicke auf **Clone** (Klonen). + + {% mac %} + + ![Die Schaltfläche „clone“ (Klonen)](/assets/images/help/desktop/clone-button-mac.png) + + {% endmac %} + + {% windows %} + + ![Die Schaltfläche „clone“ (Klonen)](/assets/images/help/desktop/clone-button-win.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/de-DE/data/reusables/desktop/cloning-location-tab.md b/translations/de-DE/data/reusables/desktop/cloning-location-tab.md index 3626b23deb..6f46075733 100644 --- a/translations/de-DE/data/reusables/desktop/cloning-location-tab.md +++ b/translations/de-DE/data/reusables/desktop/cloning-location-tab.md @@ -1 +1,13 @@ 1. Klicke auf die Registerkarte, die dem Speicherort des zu klonenden Repositorys entspricht. Du kannst auch auf **URL** klicken, um den Repository-Speicherort manuell einzugeben. + + {% mac %} + + ![Standort-Registerkarten im Menü „Clone a repository“ (Repository klonen)](/assets/images/help/desktop/choose-repository-location-mac.png) + + {% endmac %} + + {% windows %} + + ![Standort-Registerkarten im Menü „Clone a repository“ (Repository klonen)](/assets/images/help/desktop/choose-repository-location-win.png) + + {% endwindows %} diff --git a/translations/de-DE/data/reusables/desktop/cloning-repository-list.md b/translations/de-DE/data/reusables/desktop/cloning-repository-list.md index 5a8d12548a..ecd4396dd4 100644 --- a/translations/de-DE/data/reusables/desktop/cloning-repository-list.md +++ b/translations/de-DE/data/reusables/desktop/cloning-repository-list.md @@ -1 +1,14 @@ 1. Wähle in der Liste das zu klonende Repository aus. + + + {% mac %} + + ![Repository-Liste klonen](/assets/images/help/desktop/clone-a-repository-list-mac.png) + + {% endmac %} + + {% windows %} + + ![Repository-Liste klonen](/assets/images/help/desktop/clone-a-repository-list-win.png) + + {% endwindows %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/desktop/fork-type-prompt.md b/translations/de-DE/data/reusables/desktop/fork-type-prompt.md new file mode 100644 index 0000000000..1067dab748 --- /dev/null +++ b/translations/de-DE/data/reusables/desktop/fork-type-prompt.md @@ -0,0 +1,42 @@ +1. If you plan to use this fork for contributing to the original upstream repository, click **To contribute to the parent project**. + + {% mac %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/mac-fork-options-prompt.png) + + {% endmac %} + + {% windows %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/windows-fork-options-prompt.png) + + {% endwindows %} + +2. If you plan to use this fork for a project not connected to the upstream, click **For my own purposes**. + + {% mac %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/mac-fork-own-purposes.png) + + {% endmac %} + + {% windows %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/windows-fork-own-purposes.png) + + {% endwindows %} + +3. Click **Continue**. + + {% mac %} + + ![The continue button](/assets/images/help/desktop/mac-forking-continue.png) + + {% endmac %} + + {% windows %} + + ![The continue button](/assets/images/help/desktop/windows-forking-continue.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/de-DE/data/reusables/desktop/open-repository-settings.md b/translations/de-DE/data/reusables/desktop/open-repository-settings.md new file mode 100644 index 0000000000..5e298edc85 --- /dev/null +++ b/translations/de-DE/data/reusables/desktop/open-repository-settings.md @@ -0,0 +1,14 @@ +1. Open the **Repository** menu, then click **Repository settings...**. + + {% mac %} + + ![Repository settings menu option in the Mac app](/assets/images/help/desktop/mac-repository-settings.png) + + {% endmac %} + + {% windows %} + + ![Repository settings menu option in the Windows app](/assets/images/help/desktop/windows-repository-settings.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/de-DE/data/reusables/desktop/select-fork-behavior.md b/translations/de-DE/data/reusables/desktop/select-fork-behavior.md new file mode 100644 index 0000000000..11808f470f --- /dev/null +++ b/translations/de-DE/data/reusables/desktop/select-fork-behavior.md @@ -0,0 +1,28 @@ +1. Click **Fork behavior**, then select how you want to use the fork. + + {% mac %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-menu-contribute.png) + + {% endmac %} + + {% windows %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-menu-contribute.png) + + {% endwindows %} + +2. Klicke auf **Save** (Speichern). + + {% mac %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-save.png) + + {% endmac %} + + {% windows %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-save.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md b/translations/de-DE/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md new file mode 100644 index 0000000000..63fa9473e7 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md @@ -0,0 +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 including with your account. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/payment-information-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/payment-information-tab.md new file mode 100644 index 0000000000..4de0966ad7 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/payment-information-tab.md @@ -0,0 +1 @@ +1. Under "Billing", click **Payment information**. diff --git a/translations/de-DE/data/reusables/enterprise_installation/about-adjusting-resources.md b/translations/de-DE/data/reusables/enterprise_installation/about-adjusting-resources.md new file mode 100644 index 0000000000..2d6c2fe4e6 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise_installation/about-adjusting-resources.md @@ -0,0 +1 @@ +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)." diff --git a/translations/de-DE/data/reusables/enterprise_installation/aws-supported-instance-types.md b/translations/de-DE/data/reusables/enterprise_installation/aws-supported-instance-types.md index d5877937e6..703c76b30c 100644 --- a/translations/de-DE/data/reusables/enterprise_installation/aws-supported-instance-types.md +++ b/translations/de-DE/data/reusables/enterprise_installation/aws-supported-instance-types.md @@ -1,37 +1,13 @@ -{% data variables.product.prodname_ghe_server %} wird auf den folgenden EC2-Instance-Typen unterstützt. Weitere Informationen findest Du auf der [Übersichtsseite zu AWS-EC2-Instance-Typen](http://aws.amazon.com/ec2/instance-types/). +{% data variables.product.prodname_ghe_server %} is supported on the following EC2 instance sizes. Weitere Informationen findest Du auf der [Übersichtsseite zu AWS-EC2-Instance-Typen](http://aws.amazon.com/ec2/instance-types/). -| EC2-Instance-Typ | Modell | -| ---------------- | ---------------------------------- | -| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | - -| EC2-Instance-Typ | Modell | -| ---------------- | ---------------------------------- | -| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | - -| EC2-Instance-Typ | Modell | -| ---------------- | -------------------------------------------------------------------- | -| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | - -| EC2-Instance-Typ | Modell | -| ---------------- | --------------------- | -| M3 | m3.xlarge, m3.2xlarge | - -| EC2-Instance-Typ | Modell | -| ---------------- | ----------------------------------------------------------- | -| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | - -| EC2-Instance-Typ | Modell | -| ---------------- | --------------------------------------------------------------------- | -| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | - -| EC2-Instance-Typ | Modell | -| ---------------- | -------------------------------------------------------------------- | -| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | - -| EC2-Instance-Typ | Modell | -| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} - -| EC2-Instance-Typ | Modell | -| ---------------- | ------------------------ | -| X1 | x1.16xlarge, x1.32xlarge | +| Typ | Size | +|:--- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | +| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | +| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | +| M3 | m3.xlarge, m3.2xlarge | +| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | +| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | +| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | +| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} +| X1 | x1.16xlarge, x1.32xlarge | diff --git a/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index ff0495b8e9..5866ff0cda 100644 --- a/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,6 +1,5 @@ - [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} -- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} -- [Optional features](#optional-features){% endif %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %} - [Speicher](#storage) - [CPU and memory](#cpu-and-memory) @@ -8,20 +7,7 @@ We recommend different hardware configurations depending on the number of user licenses for {% data variables.product.product_location %}. If you provision more resources than the minimum requirements, your instance will perform and scale better. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - -- You must configure at least one runner for {% data variables.product.prodname_actions %} workflows. Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners)“. -- You must configure external blob storage. 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)." -- You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} 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 | Additional vCPUs | Additional memory | - |:----------------------- | ----------------:| -----------------:| - | Light testing | 4 | 30.5 GB | - | 25 | 8 | 61 GB | - | 35 | 16 | 122 GB | - | 100 | 32 | 244 GB | - -{% endif %} +{% data reusables.enterprise_installation.hardware-rec-table %} #### Speicher @@ -31,7 +17,7 @@ Your instance requires a persistent data disk separate from the root disk. Weite {% if currentVersion ver_gt "enterprise-server@2.21" %} -If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. 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)." +To configure{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you must provide external blob storage. 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)." {% endif %} @@ -39,7 +25,7 @@ You can resize your instance's root disk by building a new instance or using an #### 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. +The CPU and memory resources that {% data variables.product.prodname_ghe_server %} requires depend on the levels of activity for users, automations, and integrations. {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data reusables.actions.enterprise-hardware-considerations %}{% endif %} {% data reusables.enterprise_installation.increasing-cpus-req %} diff --git a/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md index 806110b5d1..8be47c3f35 100644 --- a/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,20 +1,20 @@ -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." +**Note**: If you joined the beta for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} and enabled the features, your instance requires additional hardware resources. 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)." {% endnote %} {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -| Benutzerlizenzen | vCPUs | Arbeitsspeicher | Attached-Storage | Root-Storage | -|:---------------------------------------------------------- | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| ------------:| -| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen | 2
or [**4**](#optional-features) | 16 GB
or [**32 GB**](#optional-features) | 100 GB
or [**150 GB**](#optional-features) | 200 GB | -| 10–3000 | 4
or [**8**](#optional-features) | 32 GB
or [**48 GB**](#optional-features) | 250 GB
or [**300 GB**](#optional-features) | 200 GB | -| 3000–5000 | 8
or [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | -| 5000–8000 | 12
or [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | -| 8000–10000+ | 16
or [**20**](#optional-features) | 128 GB
or [**160 GB**](#optional-features) | 1000 GB | 200 GB | +| Benutzerlizenzen | vCPUs | Arbeitsspeicher | Attached-Storage | Root-Storage | +|:---------------------------------------------------------- | -----:| ---------------:| ----------------:| ------------:| +| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen | 4 | 32 GB | 150 GB | 200 GB | +| 10–3000 | 8 | 48 GB | 300 GB | 200 GB | +| 3000–5000 | 12 | 64 GB | 500 GB | 200 GB | +| 5000–8000 | 16 | 96 GB | 750 GB | 200 GB | +| 8000–10000+ | 20 | 160 GB | 1000 GB | 200 GB | {% else %} @@ -28,22 +28,20 @@ {% endif %} -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)." +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +If you plan to configure {% data variables.product.prodname_actions %} for your instance, you should provision additional resources. You must also configure at least one self-hosted runner to execute workflows. 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)." + +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} #### Beta features in {% data variables.product.prodname_ghe_server %} 2.22 -You can sign up for beta features available in {% data variables.product.prodname_ghe_server %} 2.22 such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [release notes for the 2.22 series](https://enterprise.github.com/releases/series/2.22#release-2.22.0) on the {% data variables.product.prodname_enterprise %} website. +{% data variables.product.prodname_ghe_server %} 2.22 offered features in beta, such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [{% data variables.product.prodname_ghe_server %} 2.22 release notes](/enterprise-server@2.22/admin/release-notes#2.22.0). -If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". - -{% elsif currentVersion ver_gt "enterprise-server@2.22" %} - -#### Optional features - -You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. 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)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." - -If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +If you enabled beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". {% endif %} diff --git a/translations/de-DE/data/reusables/gated-features/auto-merge.md b/translations/de-DE/data/reusables/gated-features/auto-merge.md index 72a58ba07d..acfb4dddff 100644 --- a/translations/de-DE/data/reusables/gated-features/auto-merge.md +++ b/translations/de-DE/data/reusables/gated-features/auto-merge.md @@ -1 +1 @@ -Auto-merge for pull requests 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" %}{% data reusables.gated-features.more-info %}{% endif %} \ No newline at end of file +Auto-merge for pull requests 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 %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/de-DE/data/reusables/gated-features/code-scanning.md b/translations/de-DE/data/reusables/gated-features/code-scanning.md index 69e6abf27f..35598cce54 100644 --- a/translations/de-DE/data/reusables/gated-features/code-scanning.md +++ b/translations/de-DE/data/reusables/gated-features/code-scanning.md @@ -1 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled. +{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository. +{%- else %} +{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} 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 ea9376ffde..ef4050fd44 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 @@ -1,8 +1,8 @@ -| Virtuelle Umgebung | YAML-Workflow-Kennzeichnung | -| -------------------- | ------------------------------------ | -| Windows Server 2019 | `windows-latest` oder `windows-2019` | -| Ubuntu 20.04 | `ubuntu-20.04` | -| Ubuntu 18.04 | `ubuntu-latest` oder `ubuntu-18.04` | -| Ubuntu 16.04 | `ubuntu-16.04` | -| macOS Big Sur 11.0 | `macos-11.0` | -| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | +| Virtuelle Umgebung | YAML-Workflow-Kennzeichnung | +| -------------------- | -------------------------------------------- | +| Windows Server 2019 | `windows-latest` oder `windows-2019` | +| Ubuntu 20.04 | `ubuntu-latest` (see note) or `ubuntu-20.04` | +| Ubuntu 18.04 | `ubuntu-latest` (see note) or `ubuntu-18.04` | +| Ubuntu 16.04 | `ubuntu-16.04` | +| macOS Big Sur 11.0 | `macos-11.0` | +| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | diff --git a/translations/de-DE/data/reusables/github-actions/ubuntu-runner-preview.md b/translations/de-DE/data/reusables/github-actions/ubuntu-runner-preview.md index 1a3636e0e1..6eb91edc13 100644 --- a/translations/de-DE/data/reusables/github-actions/ubuntu-runner-preview.md +++ b/translations/de-DE/data/reusables/github-actions/ubuntu-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The Ubuntu 20.04 virtual environment is currently provided as a preview only. The `ubuntu-latest` YAML workflow label still uses the Ubuntu 18.04 virtual environment. +**Note:** The `ubuntu-latest` label is currently being migrated from the Ubuntu 18.04 virtual environment to Ubuntu 20.04. Specifying the `ubuntu-latest` label during the migration might use either virtual environment. To explicitly use Ubuntu 20.04 or Ubuntu 18.04, specify `ubuntu-20.04` or `ubuntu-18.04`. When the migration is complete, `ubuntu-latest` will use the Ubuntu 20.04 virtual environment. For more information about the migration, see "[Ubuntu-latest workflows will use Ubuntu-20.04](https://github.com/actions/virtual-environments/issues/1816)." {% endnote %} diff --git a/translations/de-DE/data/reusables/organizations/organizations_include.md b/translations/de-DE/data/reusables/organizations/organizations_include.md index e26cf50e5a..d78bf891f5 100644 --- a/translations/de-DE/data/reusables/organizations/organizations_include.md +++ b/translations/de-DE/data/reusables/organizations/organizations_include.md @@ -6,3 +6,4 @@ Organisationen beinhalten: - [Nested teams that reflect your company or group's structure](/articles/about-teams) with cascading access permissions and mentions{% if currentVersion != "github-ae@latest" %} - Die Möglichkeit für Organisationsinhaber, den [Zwei-Faktor-Authentifizierungsstatus (2FA)](/articles/about-two-factor-authentication) der Mitglieder anzuzeigen - The option to [require all organization members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} +{% if currentVersion == "free-pro-team@latest" %}- The option to purchase a license for {% data variables.product.prodname_GH_advanced_security %} and use the features on private repositories. {% data reusables.advanced-security.more-info-ghas %}{% endif %} diff --git a/translations/de-DE/data/reusables/pages/new-or-existing-repo.md b/translations/de-DE/data/reusables/pages/new-or-existing-repo.md index 5118c0b7ba..159b6df144 100644 --- a/translations/de-DE/data/reusables/pages/new-or-existing-repo.md +++ b/translations/de-DE/data/reusables/pages/new-or-existing-repo.md @@ -1,3 +1,5 @@ Wenn Deine Website ein unabhängiges Projekt ist, kannst Du ein neues Repository erstellen, um den Quellcode Deiner Website zu speichern. If your site is associated with an existing project, you can add the source code {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}to that project's repository, in a `/docs` folder on the default branch or on a different branch.{% else %}for your site to a `gh-pages` branch or a `docs` folder on the `master` branch in that project's repository.{% endif %} For example, if you're creating a site to publish documentation for a project that's already on {% data variables.product.product_name %}, you may want to store the source code for the site in the same repository as the project. +{% if currentVersion == "free-pro-team@latest" %}If the account that owns the repository uses {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_free_team %}, the repository must be public.{% endif %} + Wenn Du eine Website in einem vorhandenen Repository erstellen möchtest, springe zum Abschnitt „[Erstellen Deiner Website](#creating-your-site)". diff --git a/translations/de-DE/data/reusables/pull_requests/you-can-auto-merge.md b/translations/de-DE/data/reusables/pull_requests/you-can-auto-merge.md index 410aec2a8e..5da386a3d1 100644 --- a/translations/de-DE/data/reusables/pull_requests/you-can-auto-merge.md +++ b/translations/de-DE/data/reusables/pull_requests/you-can-auto-merge.md @@ -1,3 +1,3 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} You can configure a pull request to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md index 27f9b17d1c..56dcc4773f 100644 --- a/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| Schlüssel | Typ | Beschreibung | -| --------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | die Aktion, die durchgeführt wurde. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | +| Schlüssel | Typ | Beschreibung | +| --------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `string` | die Aktion, die durchgeführt wurde. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | diff --git a/translations/de-DE/data/variables/action_code_examples.yml b/translations/de-DE/data/variables/action_code_examples.yml index affbfdb18a..cf01c18912 100644 --- a/translations/de-DE/data/variables/action_code_examples.yml +++ b/translations/de-DE/data/variables/action_code_examples.yml @@ -24,7 +24,7 @@ - labels - title: Add releases to GitHub - description: Publish Github releases in an action + description: Publish GitHub releases in an action languages: 'Dockerfile, Shell' href: elgohr/Github-Release-Action tags: @@ -32,7 +32,7 @@ - publishing - title: Publish a docker image to Dockerhub - description: A Github Action used to build and publish Docker images + description: A GitHub Action used to build and publish Docker images languages: 'Dockerfile, Shell' href: elgohr/Publish-Docker-Github-Action tags: @@ -123,7 +123,7 @@ - publishing - title: Label your Pull Requests auto-magically (using committed files) - description: Github action to label your pull requests auto-magically (using committed files) + description: GitHub action to label your pull requests auto-magically (using committed files) languages: 'TypeScript, Dockerfile, JavaScript' href: Decathlon/pull-request-labeler-action tags: @@ -132,7 +132,7 @@ - labels - title: Add Label to your Pull Requests based on the author team name - description: Github action to label your pull requests based on the author name + description: GitHub action to label your pull requests based on the author name languages: 'TypeScript, JavaScript' href: JulienKode/team-labeler-action tags: diff --git a/translations/de-DE/data/variables/product.yml b/translations/de-DE/data/variables/product.yml index 20dbdcb2ac..19d4c71c57 100644 --- a/translations/de-DE/data/variables/product.yml +++ b/translations/de-DE/data/variables/product.yml @@ -147,10 +147,10 @@ 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://docs.github.com/rest{% elsif enterpriseServerVersions contains currentVersion %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif currentVersion == "github-ae@latest" %}https://docs.github.com/github-ae@latest/rest{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% endif %} #Use this inside command-line code blocks #Enterprise OAuth paths that don't include "/graphql" or "/api/v3" oauth_host_code: >- @@ -159,10 +159,10 @@ device_authorization_url: >- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}[`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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/graphql{% endif %} 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 9b55022371..271838494f 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 @@ -63,7 +63,7 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe {% data reusables.github-actions.usage-api-requests %} - **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %} -### Supported operating systems for self-hosted runners +### Supported architectures and operating systems for self-hosted runners The following operating systems are supported for the self-hosted runner application. @@ -92,6 +92,14 @@ The following operating systems are supported for the self-hosted runner applica - macOS 10.13 (High Sierra) or later +#### Architectures + +The following processor architectures are supported for the self-hosted runner application. + +- `x64` - Linux, macOS, Windows. +- `ARM64` - Linux only. +- `ARM32` - Linux only. + {% if enterpriseServerVersions contains currentVersion %} ### Supported actions on self-hosted runners 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 5073a11286..e89d2f8cf3 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 @@ -29,7 +29,7 @@ Un ejecutor auto-hospedado recibe ciertas etiquetas automáticamente cuando se a * `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. +* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. 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: diff --git a/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md index 9b6d20001d..53c0f26b3d 100644 --- a/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/es-ES/content/actions/reference/specifications-for-github-hosted-runners.md @@ -41,12 +41,17 @@ Las máquinas virtuales de Windows están configuradas para ejecutarse como admi ### Ejecutores y recursos de hardware compatibles -Cada máquina virtual tiene los mismos recursos de hardware disponibles. +Hardware specification for Windows and Linux virtual machines: - CPU de 2 núcleos - 7 GB de memoria RAM - 14 GB de espacio en el disco SSD +Hardware specification for macOS virtual machines: +- CPU de 3 núcleos +- 14 GB de memoria RAM +- 14 GB de espacio en el disco SSD + {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} @@ -71,9 +76,13 @@ Las herramientas de software que se incluyen en los ejecutores hospedados en {% Los ejecutores alojados en {% data variables.product.prodname_dotcom %} incluyen las herramientas integradas predeterminadas del sistema operativo, además de los paquetes enumerados en las referencias anteriores. Por ejemplo, los ejecutores de Ubuntu y macOS incluyen `grep`, `find` y `which`, entre otras herramientas predeterminadas. -Las bitácoras de flujo de trabajo incluyen un enlace a las herramientas preinstaladas en el ejecutor. 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)". +Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will tell you the the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -Si hay alguna herramienta que quieras solicitar, abre una propuesta en [actions/virtual-environments](https://github.com/actions/virtual-environments). +We recommend using actions to interact with the software installed on runners. This approach has several benefits: +- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters +- It ensures the tool versions used in your workflow will remain the same regardless of software updates + +Si hay alguna herramienta que quieras solicitar, abre una propuesta en [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners. ### Direcciones IP diff --git a/translations/es-ES/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/es-ES/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index 338a70ea4b..da45aefdb7 100644 --- a/translations/es-ES/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/es-ES/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -73,7 +73,7 @@ Si el servidor en donde estás ejecutando {% endif %} #### Habilitar el escaneo de código para los repositorios individuales -Después de que configuras un ejecutor auto-hospedado, {% if currentVersion == "enterprise-server@2.22" %}y aprovisionas las acciones,{% endif %} los usuarios pueden habilitar el {% data variables.product.prodname_code_scanning %} para los repositorios individuales de {% data variables.product.product_location %}. 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. +Después de que configuras un ejecutor auto-hospedado, {% if currentVersion == "enterprise-server@2.22" %}y aprovisionas las acciones,{% endif %} los usuarios pueden habilitar el {% data variables.product.prodname_code_scanning %} para los repositorios individuales de {% data variables.product.product_location %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." ### Ejecutar el {% data variables.product.prodname_code_scanning %} utilizando el {% data variables.product.prodname_codeql_runner %} Si no quieres utilizar {% data variables.product.prodname_actions %}, puedes ejecutar el {% data variables.product.prodname_code_scanning %} utilizando el {% data variables.product.prodname_codeql_runner %}. diff --git a/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index c1ada5ff63..a02426d254 100644 --- a/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md +++ b/translations/es-ES/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md @@ -20,7 +20,7 @@ Para el cifrado en tránsito, {% data variables.product.product_name %} utiliza La llave que proporciones se almacena en un módulo de seguridad de hardware (HSM) en una bóveda de llaves que administra {% data variables.product.company_short %}. -Para configurar tu llave de cifrado, utiliza la API de REST. Existen varias terminales de la API, por ejemplo, para verificar el estado de cifrado, actualiza tu llave de cifrado y bórrala. Nota que el borrar tu llave hará que tu empresa se congele. Para obtener más información acerca de las terminales de la API, consulta la sección "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST. +Para configurar tu llave de cifrado, utiliza la API de REST. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. Para obtener más información acerca de las terminales de la API, consulta la sección "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST. ### Agregar o actualizar una llave de cifrado @@ -48,24 +48,24 @@ Tu llave privada de RSA de 2048 bits deberá estar en formato PEM, por ejemplo, curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` -### Borrar tu llave de cifrado +### Disabling your encryption key -Para congelar tu empresa, por ejemplo, en caso de alguna irrupción, puedes inhabilitar el cifrado estático si borras tu llave de cifrado. +To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled. -Para descongelar tu empresa después de que hayas borrado tu llave de cifrado, contacta a soporte. Para obtener más información, consulta la sección "[Acerca de {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)". - -1. Para borrar tu llave e inhabilitar el cifrado estático, utiliza la terminal `DELETE /enterprise/encryption`. +1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently. ```shell curl -X DELETE http(s)://hostname/api/v3/enterprise/encryption ``` -2. Opcionalmente, verifica el estado de la operación de borrado. +2. Opcionalmente, verifica el estado de la operación de borrado. It takes approximately ten minutes to disable encryption at rest. ```shell curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` +To unfreeze your enterprise after you've disabled your encryption key, contact support. Para obtener más información, consulta la sección "[Acerca de {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)". + ### Leer más - "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST diff --git a/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md index 231337b03f..0f7dc70160 100644 --- a/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/es-ES/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -29,6 +29,26 @@ versions: {% endnote %} +{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %} + +### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later + +Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table. + +| Licencias de usuario | vCPU | Memoria | Almacenamiento conectado | Almacenamiento raíz | +|:---------------------------------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| -------------------:| +| Prueba, Demo o 10 usuarios no frecuentes | **4**
_Up from 2_ | **32 GB**
_Up from 16 GB_ | **150 GB**
_Up from 100 GB_ | 200 GB | +| 10-3000 | **8**
_Up from 4_ | **48 GB**
_Up from 32 GB_ | **300 GB**
_Up from 250 GB_ | 200 GB | +| 3000-5000 | **12**
_Up from 8_ | 64 GB | 500 GB | 200 GB | +| 5000-8000 | **16**
_Up from 12_ | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | **20**
_Up from 16_ | **160 GB**
_Up from 128 GB_ | 1000 GB | 200 GB | + +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% endif %} + ### 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. diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md index b204601852..475bcb0308 100644 --- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -9,13 +9,7 @@ versions: enterprise-server: '>=2.22' --- -{% if currentVersion == "enterprise-server@2.22" %} -{% note %} - -**Nota:** El soporte para {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} 2.22 es un beta público limitado. Revisa los requisitos de almacenamiento externo mencionados a continuación y [regístrate para el beta](https://resources.github.com/beta-signup/). - -{% endnote %} -{% endif %} +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} @@ -23,11 +17,33 @@ versions: Este artículo explica cómo los administradores de sitio pueden habilitar {% data variables.product.prodname_ghe_server %} para utilizar {% data variables.product.prodname_actions %}. Esto cubre los requisitos de hardware y software, presenta las opciones de almacenamiento y describe las políticas de administración de seguridad. +{% endif %} + ### Revisar las consideraciones de hardware +{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %} + +{% note %} + +**Note**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." + +{% endnote %} + +{% endif %} + {% data reusables.actions.enterprise-hardware-considerations %} -{% endif %} +For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform. + +- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) +- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) +- [Plataforma de Google Cloud](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) +- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) +- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) +- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations) +- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations) + +{% data reusables.enterprise_installation.about-adjusting-resources %} ### Requisitos de almacenamiento externo @@ -55,7 +71,7 @@ Para habilitar {% data variables.product.prodname_actions %} en {% data variable ### Habilitar {% data variables.product.prodname_actions %} -El soporte de {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} 2.22 se ecuentra en un beta público limitado. [Regístrate para el beta](https://resources.github.com/beta-signup/). +{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." ### Leer más @@ -69,7 +85,7 @@ El soporte de {% data variables.product.prodname_actions %} en {% data variables Sigue uno de los procedimientos siguientes para habilitar las {% data variables.product.prodname_actions %} con el proveedor de almacenamiento de tu elección: -* [Habilitar las GitHub Actions con Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Habilitar las GitHub Actions con el almacenamiento de Azure Blob](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) * [Habilitar las GitHub Actions con el almacenamiento de Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) * [Habilitar las GitHub Actions con la puerta de enlace de MinIO para el almacenamiento en NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) @@ -81,7 +97,7 @@ Puedes utilizar políticas para administrar el acceso a las {% data variables.pr {% data reusables.actions.enterprise-github-hosted-runners %} -Para ejecutar los flujos de trabajo de {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados. Puedes agregar ejecutores auto-hospedados a nivel de empresa, organización o repositorio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". +Para ejecutar los flujos de trabajo de {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados. Puedes agregar ejecutores auto-hospedados a nivel de empresa, organización o repositorio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)." ### Administrar qué acciones pueden utilizarse en tu empresa diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md index 24f7b6ce8e..4ace89ff72 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md @@ -8,40 +8,40 @@ versions: free-pro-team: '*' --- -### 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. +### About local repositories +Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer. + +You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. Para obtener más información, consulta la sección "[Sincronizar tu rama](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)". + +When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. Para obtener más información, visita "[Acerca de las ramificaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)." + +When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)". 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 %} +### Clonar un repositorio {% 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) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} -{% endmac %} - -{% windows %} +### Bifurcar un repositorio +If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork. {% 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) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} +{% data reusables.desktop.fork-type-prompt %} -{% endwindows %} +### Managing fork behavior +You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}. -### 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)." +{% data reusables.desktop.open-repository-settings %} +{% data reusables.desktop.select-fork-behavior %} -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) +### Leer más +- [Acerca de los repositorios remotos](/github/using-git/about-remote-repositories) diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index bf6dc75875..ee0e2801d6 100644 --- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -9,7 +9,7 @@ versions: ### 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 variables.product.prodname_desktop %} te permite crear etiquetas anotadas. Tags are associated with commits, so you can use a tag to mark an individual point in your repository's history, including a version number for a release. 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 %} @@ -44,3 +44,7 @@ versions: {% data reusables.desktop.history-tab %} {% data reusables.desktop.delete-tag %} + +### Leer más + +- "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation diff --git a/translations/es-ES/content/developers/apps/activating-beta-features-for-apps.md b/translations/es-ES/content/developers/apps/activating-beta-features-for-apps.md index ba096f63aa..1b2e033819 100644 --- a/translations/es-ES/content/developers/apps/activating-beta-features-for-apps.md +++ b/translations/es-ES/content/developers/apps/activating-beta-features-for-apps.md @@ -3,6 +3,8 @@ 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: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% warning %} diff --git a/translations/es-ES/content/developers/apps/authenticating-with-github-apps.md b/translations/es-ES/content/developers/apps/authenticating-with-github-apps.md index 421d10df69..6f924cdb8a 100644 --- a/translations/es-ES/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/es-ES/content/developers/apps/authenticating-with-github-apps.md @@ -110,7 +110,7 @@ El ejemplo anterior utiliza el tiempo de caducidad máximo de 10 minutos, despu ```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" + "documentation_url": "{% data variables.product.doc_url_pre %}" } ``` diff --git a/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 9be31f856a..3755576cdc 100644 --- a/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/es-ES/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### Introducción -Esta guía te dará una introducción a las [GitHub Apps](/apps/) y a la [API de verificaciones](/rest/reference/checks), las cuales utilizarás para crear un servidor de Integración contínua (CI) que ejecute pruebas. +This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. 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. 🙌 @@ -49,7 +49,7 @@ Para obtener una idea de lo que hará tu servidor de IC para la API de Verificac ### Prerrequisitos -Antes de que inicies, tal vez quieras familiarizarte con las [GitHub Apps](/apps/), los [Webhooks](/webhooks), y con la [API de Verificaciones](/rest/reference/checks), si aún no lo has hecho. Encontrarás más API en los [documentos de la API de REST](/rest). La API de Verificaciones también se encuentra disponible para su uso en [GraphQL](/graphql), pero este inicio rápido se enfoca en REST. Consulta los objetos de [Conjuntos de Verificaciones](/graphql/reference/objects#checksuite) y [Ejecución de Verificación](/graphql/reference/objects#checkrun) de GraphQL para obtener más detalles. +Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. Encontrarás más API en los [documentos de la API de REST](/rest). La API de Verificaciones también se encuentra disponible para su uso en [GraphQL](/graphql), pero este inicio rápido se enfoca en REST. Consulta los objetos de [Conjuntos de Verificaciones](/graphql/reference/objects#checksuite) y [Ejecución de Verificación](/graphql/reference/objects#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. @@ -203,7 +203,7 @@ Si ves otras apps en la pestaña de verificaciones, significa que tienes otras a ### 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. +Cuando tu método de `create_check_run` se ejecuta, éste solicita a GitHub crear una ejecución de verificación nueva. When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. 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. @@ -435,7 +435,7 @@ El código anterior obtiene el nombre completo del repositorio y el SHA de encab ### Paso 2.3. Ejecutar RuboCop -¡Genial! Estás clonando el repositorio y creando ejecuciones de verificación al utilizar tu servidor de IC. Now you'll get into the nitty gritty details of the [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). +¡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://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) y de las [Anotaciones de la API de Verificaciones](/rest/reference/checks#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. @@ -447,7 +447,7 @@ logger.debug @report @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. See the [RuboCop docs](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) for details and an example of the JSON format. +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://docs.rubocop.org/rubocop/formatters.html#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`. @@ -588,7 +588,7 @@ Este código limita la cantidad total de anotaciones a 50. Pero puedes modificar 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`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. +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://docs.rubocop.org/rubocop/cops.html), 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. @@ -718,7 +718,7 @@ Si las anotaciones se relacionan con un archivo que ya se incluya en la solicitu 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. -The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. 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. +La herramienta de RuboCop [ofrece](https://docs.rubocop.org/rubocop/usage/basic_usage.html#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. diff --git a/translations/es-ES/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/es-ES/content/developers/apps/migrating-oauth-apps-to-github-apps.md index fe64cdbe2e..b515e51b7b 100644 --- a/translations/es-ES/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/es-ES/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -52,7 +52,7 @@ Las GitHub Apps utilizan [reglas móviles para los límites de tasa](/apps/build #### 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/). +Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). #### Determinar los permisos que necesitará tu app @@ -62,7 +62,7 @@ En la configuración de tu GitHub App, puedes especificar si tu app necesita acc #### 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. +Después de que creaste una GitHub App nueva y seleccionaste sus permisos, puedes seleccionar los eventos de webhook a los cuales deseas suscribirte. See "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. #### Entender los diferentes métodos de autenticación diff --git a/translations/es-ES/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/es-ES/content/developers/apps/refreshing-user-to-server-access-tokens.md index 7a9ad0b1f3..5f5a4428a4 100644 --- a/translations/es-ES/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/es-ES/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,7 +42,7 @@ Esta solicitud de rellamada te enviará un token de acceso y un token de actuali { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" diff --git a/translations/es-ES/content/developers/apps/suspending-a-github-app-installation.md b/translations/es-ES/content/developers/apps/suspending-a-github-app-installation.md index 2a273623a1..d2d58300b6 100644 --- a/translations/es-ES/content/developers/apps/suspending-a-github-app-installation.md +++ b/translations/es-ES/content/developers/apps/suspending-a-github-app-installation.md @@ -5,6 +5,8 @@ redirect_from: - /apps/managing-github-apps/suspending-a-github-app-installation versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% note %} diff --git a/translations/es-ES/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/es-ES/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index 20bf68d1ee..71ea0b77a8 100644 --- a/translations/es-ES/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/es-ES/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -14,7 +14,7 @@ versions: {% 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. +If you offer a {% data variables.product.prodname_github_app %} in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate {% data variables.product.prodname_oauth_app %} to support this flow. See "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endwarning %} @@ -24,7 +24,7 @@ Antes de qeu un cliente compre tu app de {% data variables.product.prodname_mark 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`. +{% data variables.product.product_name %} then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. 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. @@ -34,27 +34,27 @@ Consulta la sección "[eventos de webhook de {% data variables.product.prodname_ ### 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. +If your app is a {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} prompts the customer to select which repositories the app can access when they purchase it. {% data variables.product.product_name %} then installs the app on the account the customer selected and grants access to the selected repositories. -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. +At this point, if you specified a **Setup URL** in your {% data variables.product.prodname_github_app %} settings, {% data variables.product.product_name %} will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your {% data variables.product.prodname_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 %}. +**Note:** The **Setup URL** is described as optional in {% data variables.product.prodname_github_app %} settings, but it is a required field if you want to offer your app in {% 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). +If your app is an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} does not install it anywhere. Instead, {% data variables.product.product_name %} redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/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`. +When a customer purchases an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `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/)". +* If your app is a {% data variables.product.prodname_github_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for {% data variables.product.prodname_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/)". +* If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)." Para cualquier tipo de app, el primer paso es redirigir al cliente a https://github.com/login/oauth/authorize. diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md index 3bea3aa51f..e86cd73a54 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -16,7 +16,7 @@ Repl.it es un ambiente de desarrollo integrado (IDE) compatible con diversos len La primera vez que el alumno d aclic en el botón para visitar Repl.it, deberá ingresar con sus credenciales de {% data variables.product.product_name %}. Después de ingresar, el alumno deberá acceder al ambiente de desarrollo que contiene el código del repositorio de tareas, completamente configurado en Repl.it. -Para obtener más información sobre cómo trabajar con Repl.it, consulta la [Guía de acceso rápido de Repl.it](https://docs.repl.it/misc/quick-start#the-repl-environment). +Para obtener más información sobre cómo trabajar con Repl.it, consulta la [Guía de acceso rápido de Repl.it](https://docs.repl.it/repls/quick-start#the-repl-environment). Para las tareas grupales, los alumnos pueden utilizar Repl.it Multiplayer para trabajar en colaboración. Para obtener más información, consulta el sitio web de [Repl.it Multiplayer](https://repl.it/site/multiplayer). diff --git a/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md index 3bfcd9b5d8..90aac30595 100644 --- a/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/es-ES/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -3,6 +3,7 @@ title: Acerca de las actualizaciones a la versión del Dependabot 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-dependabot + - /github/administering-a-repository/about-github-dependabot - /github/administering-a-repository/about-github-dependabot-version-updates versions: free-pro-team: '*' @@ -14,9 +15,9 @@ versions: 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 %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Para ciertos administradores de paquetes, {% data variables.product.prodname_dependabot_version_updates %} también es compatible con su delegación a proveedores. Las dependencias delegadas a proveedores (o almacenadas en caché) son dependencias que se verifican en un directorio específico en un repositorio en vez de que se referencien en un manifiesto. Las dependencias delegadas a proveedores están disponibles desde el momento de su creación, incluso si los servidores de paquetes no se encuentran disponibles. Las {% data variables.product.prodname_dependabot_version_updates %} pueden configurarse para verificar las dependencias delegadas a proveedores para las nuevas versiones y también pueden actualizarse de ser necesario. +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. El {% data variables.product.prodname_dependabot %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Para ciertos administradores de paquetes, {% data variables.product.prodname_dependabot_version_updates %} también es compatible con su delegación a proveedores. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Las dependencias delegadas a proveedores están disponibles desde el momento de su creación, incluso si los servidores de paquetes no se encuentran disponibles. Las {% data variables.product.prodname_dependabot_version_updates %} pueden configurarse para verificar las dependencias delegadas a proveedores para las nuevas versiones y también pueden actualizarse de ser necesario. -Cuando el {% data variables.product.prodname_dependabot %} identifica una dependencia desactualizada, levanta una solicitud de extracción para actualizar el manifiesto a su última versión de la dependencia. Para las dependencias delegadas a proveedores, el {% data variables.product.prodname_dependabot %} levanta solicitudes de cambios para reemplazar directamente la dependencia desactualizada con una versión nueva. Verificas que tu prueba pase, revisas el registro de cambios y notas de lanzamiento que se incluyan en el resumen de la solicitud de extracción y, posteriormente, lo fusionas. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". +Cuando el {% data variables.product.prodname_dependabot %} identifica una dependencia desactualizada, levanta una solicitud de extracción para actualizar el manifiesto a su última versión de la dependencia. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. 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 "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". diff --git a/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md b/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md index 5c11cdfad7..db245d53f2 100644 --- a/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/es-ES/content/github/administering-a-repository/about-protected-branches.md @@ -86,8 +86,8 @@ Puedes configurar las verificaciones de estado requeridas para que sean "laxas" | 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. | +| **Estricta** | The **Require branches to be up to date before merging** checkbox is checked. | 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** | The **Require branches to be up to date before merging** checkbox is **not** checked. | 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. | Para obtener información sobre la solución de problemas, consulta la sección "[Solucionar probelmas para las verificaciones de estado requeridas](/github/administering-a-repository/troubleshooting-required-status-checks)". diff --git a/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md b/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md index c47f3bcd40..d2440ed5cd 100644 --- a/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/about-securing-your-repository.md @@ -14,6 +14,8 @@ El primer paso para asegurar un repositorio es configurar quién puede ver y mod {% 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. +#### Available for all repositories + {% if currentVersion == "free-pro-team@latest" %} - **Política de seguridad** @@ -43,15 +45,23 @@ Utiliza {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %} + +These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} + - **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** -Visualiza cualquier secreto que - haya encontrado el {% data variables.product.prodname_dotcom %} 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). - {% endif %} + {% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else if %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. 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). + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +- **Revisión de dependencias** - Muestra todo el impacto de los cambios a las dependencias y vee los detalles de las versiones vulnerables antes de que fusiones una solicitud de cambios. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". +{% endif %} ### Explorar las dependencias La gráfica de dependencias de {% data variables.product.prodname_dotcom %} te permite explorar: @@ -59,6 +69,6 @@ La gráfica de dependencias de {% data variables.product.prodname_dotcom %} te p * 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 {% data variables.product.prodname_dependabot_alerts %} para las dependencias con vulnerabilidades de seguridad. +Debes habilitar la gráfica de dependencias antes de que {% data variables.product.prodname_dotcom %} pueda generar {% data variables.product.prodname_dependabot_alerts %} para las dependencias con vulnerabilidades de seguridad. {% if currentVersion == "free-pro-team@latest" %}Enabling the dependency graph also enables {% data variables.product.prodname_dotcom %} to run dependency reviews of pull requests.{% endif %} 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-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/es-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md index 255f113219..0e04571322 100644 --- a/translations/es-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md +++ b/translations/es-ES/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -27,13 +27,13 @@ versions: {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 4. Si no se muestra el "{% data variables.product.prodname_secret_scanning_caps %}" en la página, primero necesitarás habilitar la {% data variables.product.prodname_GH_advanced_security %}. A la derecha de "{% data variables.product.prodname_GH_advanced_security %}", da clic en **Habilitar**. ![Habilitar la {% data variables.product.prodname_GH_advanced_security %} para tu repositorio](/assets/images/help/repository/enable-ghas-dotcom.png) 5. Da clic en **Habilitar la {% data variables.product.prodname_GH_advanced_security %} para este repositorio** para confirmar la acción. ![Confirmar la habilitación de la {% data variables.product.prodname_GH_advanced_security %} para tu repositorio](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) 6. Cuando habilitas la {% data variables.product.prodname_GH_advanced_security %}, esto podría habilitar el {% data variables.product.prodname_secret_scanning %} automáticamente para el repositorio (esto se controla en la configuración de la organización). Si se muestra "{% data variables.product.prodname_secret_scanning_caps %}" con un botón de **Habilitar**, aún necesitarás habilitar el {% data variables.product.prodname_secret_scanning %} si das clic en **Habilitar**. Si ves un botón de **Inhabilitar**, entonces el {% data variables.product.prodname_secret_scanning %} ya se encuentra habilitado. - ![Habilitar el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Habilitar el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/help/repository/enable-secret-scanning-dotcom.png) + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} 4. A la derecha de " {% data variables.product.prodname_secret_scanning_caps %}", da clic en **Habilitar**. ![Habilitar el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/help/repository/enable-secret-scanning-ghe.png) diff --git a/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index de0a3bb3c7..3513ffbe92 100644 --- a/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -4,13 +4,12 @@ intro: "Puedes permitir o dejar de permitir la fusión automática de solicitude product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' permissions: Las personas con permisos de mantenedor pueden administrar las fusiones automáticas de solicitudes de cambios en un repositorio. --- -{% data reusables.pull_requests.auto-merge-release-phase %} - Si permites la fusión automática de solciitudes de cambios en tu repositorio, las personas pueden configurar que solicitudes de cambio individuales en éste se fusionen automáticamente cuando todos los requisitos de fusión se cumplan. Para obtener más información, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Debajo de "Botón para fusionar", selecciona o deselecciona **Permitir la fusión automática**. ![Casilla de verificación para permitir o dejar de permitir la fusión automática](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) \ No newline at end of file +1. Debajo de "Botón para fusionar", selecciona o deselecciona **Permitir la fusión automática**. ![Casilla de verificación para permitir o dejar de permitir la fusión automática](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) diff --git a/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index efe02d3e33..ee57fad8d7 100644 --- a/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -33,10 +33,15 @@ Puedes administrar las características de seguridad y de análisis para tu 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**. -{% if currentVersion == "free-pro-team@latest" %}Si no se muestra "{% data variables.product.prodname_secret_scanning_caps %}", puede que primero necesites habilitar la {% data variables.product.prodname_GH_advanced_security %}. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. ![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-dotcom-private.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} +**Note:** If you disable + + {% data variables.product.prodname_GH_advanced_security %}, both {% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail. + {% endnote %} + + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} ![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-ghe.png) {% endif %} diff --git a/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md b/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md index d1b3be621c..3d9c2ce284 100644 --- a/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md +++ b/translations/es-ES/content/github/administering-a-repository/securing-your-repository.md @@ -6,5 +6,6 @@ redirect_from: - /articles/securing-your-repository versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- diff --git a/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md b/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md index 9215b586b3..926a6d8bf8 100644 --- a/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/es-ES/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,7 +24,7 @@ Te recomendamos revisar las siguientes consideraciones antes de que cambies la v * Si cambias la visibilidad de un repositorio de interna a privada, {% data variables.product.prodname_dotcom %} eliminará las bifurcaciones que pertenezcan a cualquiera de los usuarios sin acceso al repositorio que recientemente se hizo privado. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}La visibilidad de cualquier bifurcación también cambiará a privada.{% elsif currentVersion == "github-ae@latest" %}Si el repositorio interno tiene cualquier bifurcación, la visibilidad de éstas ya será privada.{% endif %} Para obtener más información, consulta la sección "[¿Qué pasa con las bifurcaciones cuando un repositorio se borra o cambia su visibilidad?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} * Si utilizas {% data variables.product.prodname_free_user %} para cuentas de usuario o de organización, algunas características no estarán disponibles en el repositorio después de que cambies la visibilidad a privada. {% data reusables.gated-features.more-info %}{% endif %} * Cualquier sitio de {% data variables.product.prodname_pages %} publicado se dejará de publicar automáticamente.{% if currentVersion == "free-pro-team@latest" %} Si agregaste un dominio personalizado al sitio de {% data variables.product.prodname_pages %}, deberás eliminar o actualizar tus registros de DNS antes de que hagas al repositorio privado para evitar el riesgo de que alguien más tome el dominio. Para obtener más información, consulta la sección "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} ya no incluirá el repositorio en el {% data variables.product.prodname_archive %}. Para obtener más información, consulta la sección "[Acerca de archivar el 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" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_dotcom %} ya no incluirá el repositorio en el {% data variables.product.prodname_archive %}. For more information, 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} * Las características de la {% data variables.product.prodname_GH_advanced_security %}, tales como el {% data variables.product.prodname_code_scanning %}, dejarán de funcionar a menos de que el repositorio pertenezca a una organización que tenga una licencia para la {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * El acceso anónimo de Git ya no está disponible. Para obtener más información, consulta la sección "[Habilitar el acceso de lectura anónima en Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)".{% endif %} diff --git a/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md index c089d56e49..f5e1703d63 100644 --- a/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md +++ b/translations/es-ES/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md @@ -33,14 +33,18 @@ Si estás usando una llave GPG que coincida con la identidad de la persona que c Comment: GitHub key Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? ``` -7. Escribe `O` para guardar tus selecciones. +7. Enter `O` to confirm your selections. 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`: +9. Enter `gpg> save` to save the changes + ```shell + $ gpg> save + ``` +10. 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). +11. Carga la llave GPG al [agregarla a tu cuenta GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). ### Leer más diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index 265368867f..7394b73599 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -4,10 +4,9 @@ intro: 'Puedes incrementar la velocidad de desarrollo si habilitas la fusión au product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' --- -{% data reusables.pull_requests.auto-merge-release-phase %} - ### Acerca de la fusión automática Si habilitas la fusión automática para una solicitud de cambios, ésta se fusionará automáticamente cuando se cumplan todas las revisiones requeridas y cuando todas las verificaciones de estado hayan pasado. La fusión automática te evita el esperar a que los requisitos se cumplan para que puedas continuar con otras tareas. diff --git a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index e2e3d7aeca..0e6720009b 100644 --- a/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -9,7 +9,6 @@ versions: github-ae: '*' --- - ### 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. 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. Sin embargo, puede que existan restricciones sobre cuándo puedes fusionar una solicitud de cambios 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)". diff --git a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index 30c3845e18..00aaf6da43 100644 --- a/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/es-ES/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -23,7 +23,7 @@ Cuando alguien con permisos administrativos o de propietario ha activado las rev {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Si un equipo habilitó las asignaciones de revisión de código, las aprobaciones individuales no serán suficientes para el requisito de obtener la 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 == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Si un archivo tiene un propietario del código, puedes ver quién es éste antes de que abras una solicitud de extracción. En el repositorio, puedes buscar el archivo y pasar el puntero del mouse por encima {% octicon "shield-lock" aria-label="The edit icon" %}. diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 1e83e9fea2..4a985894e0 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -134,19 +134,22 @@ Intenta compilar el código para los lenguajes compilados de C/C++, C#, y Java. Analiza el código en las bases de datos de {% data variables.product.prodname_codeql %} y carga los resultados a {% data variables.product.product_location %}. -| Marcador | Requerido | Valor de entrada | -| -------------------------------- |:---------:| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--repositorio` | ✓ | Nombre del repositorio que se analizará. | -| `--commit` | ✓ | SHA de la confirmación que se analizará. En Git y en Azure DevOps, este corresponde al valor de `git rev-parse HEAD`. En Jenkins, este corresponde a `$GIT_COMMIT`. | -| `--ref` | ✓ | Nombre de la referencia a analizar, por ejemplo `refs/heads/main`. En Git y en Jenkins, esto corresponde al valor de `git symbolic-ref HEAD`. En Azure DevOps, esto corresponde a `$(Build.SourceBranch)`. | -| `--github-url` | ✓ | URL de la instancia de {% data variables.product.prodname_dotcom %} donde se hospeda tu repositorio. | -| `--github-auth` | ✓ | Un token de {% data variables.product.prodname_github_apps %} o un token de acceso personal. | -| `--checkout-path` | | La ruta a la confirmación de salida de tu repositorio. El predeterminado es el directorio de trabajo. | -| `--no-upload` | | Ninguno. Impide que el {% data variables.product.prodname_codeql_runner %} cargue los resultados a {% data variables.product.product_location %}. | -| `--output-dir` | | Directorio en donde se almacenan los archivos SARIF de salida. El predeterminado está en el directorio de archivos temporales. | -| `--temp-dir` | | Directorio donde se almacenan los archivos temporales. El predeterminado es _./codeql-runner_. | -| `--debug` | | Ninguno. Imprime una salida más verbosa. | -| `-h`, `--help` | | Ninguno. Muestra la ayuda para el comando. | +| Marcador | Requerido | Valor de entrada | +| ---------------------------------- |:---------:| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `--repositorio` | ✓ | Nombre del repositorio que se analizará. | +| `--commit` | ✓ | SHA de la confirmación que se analizará. En Git y en Azure DevOps, este corresponde al valor de `git rev-parse HEAD`. En Jenkins, este corresponde a `$GIT_COMMIT`. | +| `--ref` | ✓ | Nombre de la referencia a analizar, por ejemplo `refs/heads/main`. En Git y en Jenkins, esto corresponde al valor de `git symbolic-ref HEAD`. En Azure DevOps, esto corresponde a `$(Build.SourceBranch)`. | +| `--github-url` | ✓ | URL de la instancia de {% data variables.product.prodname_dotcom %} donde se hospeda tu repositorio. | +| `--github-auth` | ✓ | Un token de {% data variables.product.prodname_github_apps %} o un token de acceso personal. | +| `--checkout-path` | | La ruta a la confirmación de salida de tu repositorio. El predeterminado es el directorio de trabajo. | +| `--no-upload` | | Ninguno. Impide que el {% data variables.product.prodname_codeql_runner %} cargue los resultados a {% data variables.product.product_location %}. | +| `--output-dir` | | Directorio en donde se almacenan los archivos SARIF de salida. El predeterminado está en el directorio de archivos temporales. | +| `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. | +| `--no-add-snippets` | | Ninguno. Excludes code snippets from the SARIF output. | +| `--threads` | | Number of threads to use when running queries. The default is to use all available cores. | +| `--temp-dir` | | Directorio donde se almacenan los archivos temporales. El predeterminado es _./codeql-runner_. | +| `--debug` | | Ninguno. Imprime una salida más verbosa. | +| `-h`, `--help` | | Ninguno. Muestra la ayuda para el comando. | #### `cargar` diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md index 86a83ee68d..1e3ac9e15e 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md @@ -17,7 +17,7 @@ versions: ### Acerca de {% data variables.product.prodname_codeql_workflow %} y los lenguajes compilados -Habilitas {% data variables.product.prodname_dotcom %} para que ejecute el {% data variables.product.prodname_code_scanning %} para tu repositorio si agregas un flujo de trabajo de {% data variables.product.prodname_actions %} a éste. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. 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. +You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} Para obtener información general acerca de cómo configurar diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md index 585412abaf..a3c0f7a5ba 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md @@ -14,7 +14,7 @@ versions: {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %} {% link_in_list /about-code-scanning %} {% link_in_list /triaging-code-scanning-alerts-in-pull-requests %} - {% link_in_list /enabling-code-scanning %} + {% link_in_list /setting-up-code-scanning-for-a-repository %} {% link_in_list /managing-code-scanning-alerts-for-your-repository %} {% link_in_list /configuring-code-scanning %} {% link_in_list /configuring-the-codeql-workflow-for-compiled-languages %} diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 63170bfc95..5146df2f82 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -16,7 +16,7 @@ redirect_from: ### Acerca de las alertas de {% data variables.product.prodname_code_scanning %} -Puedes configurar el {% data variables.product.prodname_code_scanning %} para que verifique el código en un repositorio utilizando el análisis predeterminado de {% data variables.product.prodname_codeql %}, un análisis de terceros, o varios tipos de análisis. Cuando se complete el análisis, las alertas resultantes se mostrarán unas junto a otras en la vista de seguridad del repositorio. Los resultados de las herramientas de terceros o de las consultas personalizadas podrían no incluir todas las propiedades que ves para las alertas que se detectan con el análisis predeterminado del {% data variables.product.prodname_codeql %} de {% data variables.product.company_short %}. 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. +Puedes configurar el {% data variables.product.prodname_code_scanning %} para que verifique el código en un repositorio utilizando el análisis predeterminado de {% data variables.product.prodname_codeql %}, un análisis de terceros, o varios tipos de análisis. Cuando se complete el análisis, las alertas resultantes se mostrarán unas junto a otras en la vista de seguridad del repositorio. Los resultados de las herramientas de terceros o de las consultas personalizadas podrían no incluir todas las propiedades que ves para las alertas que se detectan con el análisis predeterminado del {% data variables.product.prodname_codeql %} de {% data variables.product.company_short %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." Predeterminadamente, el {% data variables.product.prodname_code_scanning %} analiza tu código periódicamente en la rama predeterminada y durante las solicitudes de cambios. Para obtener información acerca de la administración de alertas en una solicitud de cambios, consulta la sección "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". @@ -28,7 +28,7 @@ Cada alerta resalta un problema en el código y el nombre de la herramienta que ![Ejemplo de alerta de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) -Si habilitas el {% data variables.product.prodname_code_scanning %} utilizando {% data variables.product.prodname_codeql %}, esto también detectará problemas de flujo de datos en tu código. El análisis de flujo de datos encuentra problemas de seguridad potenciales en el código, tales como: utilizar los datos de formas no seguras, pasar argumentos peligrosos a las funciones y tener fugas de información sensible. +If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. El análisis de flujo de datos encuentra problemas de seguridad potenciales en el código, tales como: utilizar los datos de formas no seguras, pasar argumentos peligrosos a las funciones y tener fugas de información sensible. 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. @@ -65,7 +65,7 @@ Cerrar una alerta es una forma de resolverla si no crees que necesita un arreglo ### Descartar o borrar las alertas -Hay dos formas de cerrar una alerta. Puedes arreglar el problema en el código, o puedes descartar la alerta. Como alternativa, si tienes permisos adminsitrativos en el repositorio, puedes borrar las alertas. Borrar las alertas es úti en situaciones en donde habilitaste una herramienta de {% data variables.product.prodname_code_scanning %} y después decidiste eliminarla, o cuando habilitas el análisis de {% data variables.product.prodname_codeql %} con un conjunto más grande de consultas del que quieres seguir utilizando y luego eliminaste algunas de las consultas de esa herramienta. En ambos casos, el borrar las alertas te permite limpiar tus resultados del {% data variables.product.prodname_code_scanning %}. Puedes borrar las alertas de la lista de resumen dentro de la pestaña de **Seguridad**. +Hay dos formas de cerrar una alerta. Puedes arreglar el problema en el código, o puedes descartar la alerta. Como alternativa, si tienes permisos adminsitrativos en el repositorio, puedes borrar las alertas. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. En ambos casos, el borrar las alertas te permite limpiar tus resultados del {% data variables.product.prodname_code_scanning %}. Puedes borrar las alertas de la lista de resumen dentro de la pestaña de **Seguridad**. El descartar una alerta es una forma de cerrar aquellas que no crees que necesiten arreglo. {% data reusables.code-scanning.close-alert-examples %} Puedes eliminar alertas desde las anotaciones del {% data variables.product.prodname_code_scanning %} en el código, o desde la lista de resumen dentro de la pestaña de **Seguridad**. @@ -127,5 +127,5 @@ Si un proyecto tiene varias alertas que quieras descartar por la misma razón, p ### Leer más - "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)" -- "[Habilitar el {% data variables.product.prodname_code_scanning %} para un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)" +- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" - "[Acerca de la integración con {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)" diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 029c632e4c..7b56dcbcdd 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -24,7 +24,7 @@ Si utilizas un sistema de integración contínua o de desliegue/entrega contínu {% 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 %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". -Puedes utilizar el {% data variables.product.prodname_codeql_runner %} 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. Como alternativa, puedes utilizar {% data variables.product.prodname_actions %} para ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Habilitar el {% data variables.product.prodname_code_scanning %} para un repositorio](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)". +Puedes utilizar el {% data variables.product.prodname_codeql_runner %} 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. Como alternativa, puedes utilizar {% data variables.product.prodname_actions %} para ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_location %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." El {% data variables.product.prodname_codeql_runner %} es una herramienta de línea de comandos que ejecuta un análisis de {% data variables.product.prodname_codeql %} en un control de un repositorio de {% data variables.product.prodname_dotcom %}. Agregas el ejecutor a tu sistema de terceros y luego lo llamas para que analice el código y cargue los resultados a {% data variables.product.product_location %}. Estos resultados se muestran como alertas del {% data variables.product.prodname_code_scanning %} en el repositorio. diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md new file mode 100644 index 0000000000..c23538ba91 --- /dev/null +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -0,0 +1,121 @@ +--- +title: Setting up code scanning for a repository +shortTitle: Setting up code scanning +intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.' +redirect_from: + - /github/managing-security-vulnerabilities/configuring-automated-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} + +### Options for setting up {% data variables.product.prodname_code_scanning %} + +You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to 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 %} + +### Setting up {% 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 %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/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) +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. As a result, {% data variables.product.prodname_code_scanning %} will now commence. + +### 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. 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. + +### 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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. + + ![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 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. + +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, 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 setting up {% 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 set up {% 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-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index 6bafe08098..bb1c80c3c3 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -15,7 +15,7 @@ versions: 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". -Si el {% data variables.product.prodname_code_scanning %} presenta cualquier resultado con una severidad de `error`, la verificación fallará y el error se reportará en los resultados de la verificación. Si todos los resultados que encuentra el {% data variables.product.prodname_code_scanning %} tienen severidades menores, las alertas se tratarán como advertencias o notificaciones y la verificación será exitosa. Si tu solicitud de cambios apunta a una rama protegida que se habilitó para el {% data variables.product.prodname_code_scanning %} y el propietario del repositorio configuró las verificaciones de estado requeridas, entonces debes ya sea arreglar o {% if currentVersion == "enterprise-server@2.22" %}cerrar{% else %}descartar{% endif %} todas las alertas de error antes de que se pueda 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)". +Si el {% data variables.product.prodname_code_scanning %} presenta cualquier resultado con una severidad de `error`, la verificación fallará y el error se reportará en los resultados de la verificación. Si todos los resultados que encuentra el {% data variables.product.prodname_code_scanning %} tienen severidades menores, las alertas se tratarán como advertencias o notificaciones y la verificación será exitosa. 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 you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". ![Verificación fallida del {% data variables.product.prodname_code_scanning %} en una solicitud de cambios](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 3fc6ba15b3..dbdd7a0f84 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -75,7 +75,7 @@ Cuando ### Acceso a las alertas de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% else %}seguridad{% endif %} del {% data variables.product.prodname_dependabot %} -Puedes ver todas las alertas que afectaron un proyecto en particular{% if currentVersion == "free-pro-team@latest" %} en la pestaña de seguridad del repositorio o{% endif %} en la gráfica de dependencias del mismo.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Visualizar y actualizar las dependencias vulnerables en tu repositorio](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)".{% endif %} +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](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} Predeterminadamente, notificamos a las personas con permisos adminsitrativos en los repositorios afectados sobre las @@ -89,6 +89,11 @@ Enviamos alertas de seguridad para las personas con permisos de administrador en {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} Para obtener más información, consulta la sección "[Elegir el método de entrega para tus notificaciones](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)".{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} Para obtener más información, consulta la sección "[Configurar las notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)".{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +You can also see all the +{% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in 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#viewing-your-vulnerable-repositories)." +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} ### Leer más diff --git a/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md index 5f4d7dd049..f70e8ff76b 100644 --- a/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/es-ES/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -24,7 +24,7 @@ El nivel de gravedad es uno de cuatro niveles posibles definidos en el [Sistema - 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. +La {% data variables.product.prodname_advisory_database %} utiliza estándares de CVSS versión 3.0 y los niveles de CVSS descritos anteriormente. {% data reusables.repositories.github-security-lab %} @@ -41,7 +41,8 @@ También se puede acceder a la base de datos utilizando la API de GraphQL. Para {% 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. + +You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} @@ -49,16 +50,30 @@ Puedes buscar coincidencias exactas en la base de datos y utilizar calificadores | Qualifier | Ejemplo | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `GHSA-ID` | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | +| `CVE-ID` | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | | `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. | +| `cwe:ID` | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | +| `credit:USERNAME` | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | | `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. | +| `created:YYYY-MM-DD` | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) mostrará únicamente las asesorías creadas en esta fecha. | +| `updated:YYYY-MM-DD` | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) mostrará únicamente asesorías actualizadas en esta fecha. | + +### Viewing your vulnerable repositories + +For any vulnerability in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories have a {% data variables.product.prodname_dependabot %} alert for that vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. 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#access-to-dependabot-alerts)". + +1. Navega hasta https://github.com/advisories. +2. Click an advisory. +3. At the top of the advisory page, click **Dependabot alerts**. ![Las alertas del dependabot](/assets/images/help/security/advisory-database-dependabot-alerts.png) +4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) +5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name. ### Leer más diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index 6c26774334..e9debb2f3e 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -12,6 +12,8 @@ versions: {% data reusables.github-actions.actions-spending-limit-brief %} Para obtener más información, consulta la sección "[Acerca de los límites de gasto](#about-spending-limits)". +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 %} usage beyond the amounts including with your account. 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)." + Los minutos se restablecen cada mes, pero no es el caso para el uso de almacenamiento. | Producto | Almacenamiento | Minutos (por mes) | diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 92a241a7ee..c00c5ce816 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.package_registry.container-registry-beta-billing-note %} +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_registry %} usage beyond the amounts including with your account. 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)." + La transferencia de datos se restablece cada mes, pero no así el uso de almacenamiento. | Producto | Almacenamiento | Transferencia de datos (por mes) | diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 28cb039901..c2022b4ad5 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %}Para obtener más información acerca de los costos de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de los costos de {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". +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 %} usage beyond the amounts including with your account. 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)." + Tan pronto como configures un límite de gastos diferente a $0, serás responsable de cualquier uso excedente que se suscite en el periodo de facturación actual. 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 crear un artefacto de un flujo de trabajo fallará. No recibirás una cuenta por esos 0.1GB extras en ese mes. Sin embargo, si habilitas los excedentes, tu primer factura incluirá el excedente de 0.1GB del ciclo de facturación actual, así como cualquier otro excedente que acumules. diff --git a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index ab30259d8d..61e330a93a 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/es-ES/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %}Para obtener más información acerca de los costos de utilización de {% data variables.product.prodname_registry %}, consulta la sección "[Acerca de los costos de {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". +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_registry %} usage beyond the amounts including with your account. 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)." + Tan pronto como configures un límite de gastos diferente a $0, serás responsable de cualquier uso excedente que se suscite en el periodo de facturación actual. 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, tu primer factura incluirá el excedente de 0.1GB del ciclo de facturación actual, así como cualquier otro excedente que acumules. diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 8fcefb9f34..d89f0282e6 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -23,8 +23,13 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -La página que se muestra te permite habilitar o inhabilitar todas las características de seguridad y de análisis para los repositorios de tu organización. {% if currentVersion == "free-pro-team@latest" %}Si tu organización, o la empresa a la que pertenece, tiene una licencia para {% data variables.product.prodname_GH_advanced_security %}, la págna también contendrá opciones para habilitar e inhabilitar las características de {% data variables.product.prodname_advanced_security %}. +La página que se muestra te permite habilitar o inhabilitar todas las características de seguridad y de análisis para los repositorios de tu organización. +{% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@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.{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Características de la {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) {% endif %} @@ -42,24 +47,21 @@ Puedes habilitar o inhabilitar las características para todos los repositorios. 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 "Configurar las características de seguridad y análisis", a la derecha de la característica, da clic en **Inhabilitar todo** o **Habilitar todo**. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![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-ghe.png) {% endif %} 2. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos en tu organización. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) {% endif %} -1. 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. - {% if currentVersion == "free-pro-team@latest" %} +3. 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. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Botón para inhabilitar o habilitar la característica](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Botón para inhabilitar o habilitar la característica](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) {% endif %} @@ -68,10 +70,9 @@ Puedes habilitar o inhabilitar las características para todos los repositorios. 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 "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 {% if currentVersion == "free-pro-team@latest" %}, o para todos los repositorios privados nuevos,{% endif %} en tu organización. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![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-ghe.png) {% endif %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 4ff360d9b1..f53650638a 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/es-ES/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -70,7 +70,7 @@ Además de administrar los parámetros al nivel de la organización, los propiet {% 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** |{% if currentVersion == "free-pro-team@latest" %} +| Elegir, reabrir y asignar todas las propuestas y solicitudes de extracción | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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** | @@ -150,8 +150,8 @@ En esta sección, puedes encontrar los niveles de permisos de repositorios que s | 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-security-alerts) para las dependencias vulnerables | | | | | **X** | -| Crear [asesorías de seguridad](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | -| Administrar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %} (consulta la sección "[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)") | | | | | **X** | +| Crear [asesorías de seguridad](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| Administrar el acceso a las características de la {% data variables.product.prodname_GH_advanced_security %} (consulta la sección "[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)") | | | | | **X** |{% endif %}{% 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** | | [Ver las revisiones de las dependencias](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | [Ver las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md new file mode 100644 index 0000000000..ea9b3d4b19 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md @@ -0,0 +1,40 @@ +--- +title: Connecting an Azure subscription to your enterprise +intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the included amounts for your enterprise.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise +versions: + free-pro-team: '*' +--- + +### About Azure subscriptions and {% data variables.product.product_name %} + +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 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) and "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." + +After you connect an Azure subscription, you can also manage your spending limit. For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)" and "[Managing your spending limit for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)." + +### Connecting your Azure subscription to your enterprise account + +To connect your Azure subscription, you must have owner permissions to the subscription. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Payment Information", click **Add Azure Subscription**. +1. To sign in to your Microsoft account, follow the prompts. +1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**. +1. Under "Select a subscription", select the Azure Subscription ID that you want to connect to your enterprise. +1. Click **Connect**. + +### Disconnecting your Azure subscription from your enterprise account + +After you disconnect your Azure subscription from your enterprise account, your usage can no longer exceed the amounts included with your plan. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. +1. Review the prompt, then click **Remove**. 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 e45867ba90..e47229ed40 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 @@ -18,6 +18,7 @@ versions: {% link_in_list /about-enterprise-accounts %} {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %} {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %} + {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %} {% topic_link_in_list /managing-users-in-your-enterprise %} {% link_in_list /roles-in-an-enterprise %} {% link_in_list /inviting-people-to-manage-your-enterprise %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md index 0e13245594..85499d4028 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md @@ -31,7 +31,7 @@ Los propietarios de las empresas tienen el control absoluto de las mismas y pued 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. De forma similar, los propietarios de las organizaciones en tu empresa no tienen acceso a la empresa misma a menos de que los conviertas en propietarios de ella. -Puedes agregar tantos propietarios de la empresa como quieras. {% if currentVersion == "free-pro-team@latest" %}Los propietrios de la empresa deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}.{% endif %} Como mejor práctica, te recomendamos que solo algunas personas en tu compañía se conviertan en propietarios, para reducir el riesgo en tu negocio. +An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. {% if currentVersion == "free-pro-team@latest" %}Los propietrios de la empresa deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}.{% endif %} Como mejor práctica, te recomendamos que solo algunas personas en tu compañía se conviertan en propietarios, para reducir el riesgo en tu negocio. ### Miembros de empresa @@ -52,7 +52,7 @@ Los gerentes de facturación solo tienen acceso a la configuración de facturaci - 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 empresa y no pueden agregar o eliminar propietarios de la misma. Los gerentes de facturación deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}. +Billing managers will only consume a license if they are an owner or member of at least one organization within the enterprise. Los gerentes de facturación no tienen acceso a las organizaciones o repositorios de tu empresa y no pueden agregar o eliminar propietarios de la misma. Los gerentes de facturación deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}. ### Leer más diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 6c11b6a96d..ac7e48cdc9 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -15,6 +15,8 @@ versions: 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 %}). +{% if currentVersion == "free-pro-team@latest" %}{% 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)."{% endif %} + Para obtener más información acerca de administrar a los gerentes de facturación, consulta la sección "[Invitar a las personas a administrar tu empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". ### Ver la suscripción y el uso de tu cuenta de empresa diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index c27f0ad497..ab325c4f54 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -50,7 +50,7 @@ El propietario del repositorio tiene control completo del repositorio. Adicional | 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 | "[Acerca de archivar los repositorios](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | 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)" | +| Mostrar el botón del patrocinador | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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 %} ### Acceso de colaborador para un repositorio que pertenezca a una cuenta de usuario diff --git a/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index 29a0b888d6..7a1396883c 100644 --- a/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -25,8 +25,6 @@ Antes de que puedas usar Jekyll para crear un sitio de {% data variables.product {% 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 %} @@ -36,6 +34,8 @@ Antes de que puedas usar Jekyll para crear un sitio de {% data variables.product {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% data reusables.command_line.open_the_multi_os_terminal %} 2. Si aún no tienes una copia local de tu repositorio, desplázate hasta la ubicación en la que quieras almacenar los archivos fuente de tu sitio y reemplaza _PARENT-FOLDER_ por la carpeta que quieras que contenga la carpeta para su repositorio. ```shell diff --git a/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site.md b/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site.md index a7ab29bad3..767197a8aa 100644 --- a/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site.md +++ b/translations/es-ES/content/github/working-with-github-pages/creating-a-github-pages-site.md @@ -20,8 +20,6 @@ versions: {% 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 %} @@ -33,6 +31,8 @@ versions: {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% 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. diff --git a/translations/es-ES/content/rest/overview/libraries.md b/translations/es-ES/content/rest/overview/libraries.md index f58efb6702..7ffe9cb0aa 100644 --- a/translations/es-ES/content/rest/overview/libraries.md +++ b/translations/es-ES/content/rest/overview/libraries.md @@ -25,7 +25,7 @@ versions: ### Clojure -Nombre de biblioteca | Repositorio |---|---| **Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles) +Library name | Repository |---|---| **Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles) ### Dart @@ -57,7 +57,7 @@ Nombre de biblioteca | Repositorio | |---|---| **Biblioteca de NodeJS de GitHub* ### Julia -Nombre de biblioteca | Repositorio | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl) +Library name | Repository | |---|---| **GitHub.jl**|[WestleyArgentum/GitHub.jl](https://github.com/WestleyArgentum/GitHub.jl) ### OCaml @@ -65,11 +65,11 @@ Nombre de biblioteca | Repositorio | |---|---| **ocaml-github**|[mirage/ocaml-gi ### Perl -Nombre de biblioteca | Repositorio | Sitio Web de metacpan de la biblioteca |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub) +Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub) ### PHP -Nombre de biblioteca | Repositorio |---|---| **Cliente PHP de GitHub **|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **API de PHP de GitHub**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **API de GitHub**|[yiiext/github-api](https://github.com/yiiext/github-api) **Paquete de GitHub Joomla! **|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **Extensión de Nette de GitHub**|[kdyby/github](https://github.com/kdyby/github) **Acceso Fácil a la API de GitHub API**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge para Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **Cliente de PHP7 & wrapper de WebHook**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI) +Nombre de biblioteca | Repositorio |---|---| **Cliente PHP de GitHub **|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **API de PHP de GitHub**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **API de GitHub**|[yiiext/github-api](https://github.com/yiiext/github-api) **Paquete de GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GitHubAPI](https://github.com/FlexyProject/GitHubAPI) ### Python diff --git a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md index 6f6e6e75f0..ef67cf2400 100644 --- a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md @@ -129,7 +129,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar > { > "message": "Bad credentials", -> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -141,7 +141,7 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f > 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" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -358,7 +358,7 @@ Si excedes el límite de tasa, se regresará una respuesta de error: > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#rate-limiting" > } ``` @@ -403,7 +403,7 @@ Si tu aplicación activa este límite de tasa, recibirás una respuesta informat > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#abuse-rate-limits" > } ``` diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md index 3ea95867a0..9acdb60075 100644 --- a/translations/es-ES/content/rest/reference/repos.md +++ b/translations/es-ES/content/rest/reference/repos.md @@ -141,7 +141,7 @@ Nota que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) `repo_dep ### 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. +When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository to the same environment name will become `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. diff --git a/translations/es-ES/data/reusables/actions/enterprise-beta.md b/translations/es-ES/data/reusables/actions/enterprise-beta.md index 863c6f6bad..0c674122af 100644 --- a/translations/es-ES/data/reusables/actions/enterprise-beta.md +++ b/translations/es-ES/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,12 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**Nota:** El soporte para {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} 2.22 es un beta público limitado. Para revisar los requisitos de almacenamiento externo y solicitar acceso al beta, 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)". +**Note:** {% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. The beta has ended. {% data variables.product.prodname_actions %} is now generally available in {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +
+ +- For more information about upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." +- For more information about configuring {% data variables.product.prodname_actions %} after you upgrade, see the [documentation for {% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server). {% endnote %} {% endif %} diff --git a/translations/es-ES/data/reusables/actions/enterprise-common-prereqs.md b/translations/es-ES/data/reusables/actions/enterprise-common-prereqs.md index 663db2d0c0..dd932a3679 100644 --- a/translations/es-ES/data/reusables/actions/enterprise-common-prereqs.md +++ b/translations/es-ES/data/reusables/actions/enterprise-common-prereqs.md @@ -1,4 +1,4 @@ -* {% data reusables.actions.enterprise-hardware-considerations %} +* Review the hardware requirements for {% data variables.product.prodname_actions %}. 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#review-hardware-considerations)". * Se debe configurar el TLS para el dominio de {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Configurar el TLS](/admin/configuration/configuring-tls)". {% note %} diff --git a/translations/es-ES/data/reusables/actions/enterprise-hardware-considerations.md b/translations/es-ES/data/reusables/actions/enterprise-hardware-considerations.md index 392ab96a85..98ac65f438 100644 --- a/translations/es-ES/data/reusables/actions/enterprise-hardware-considerations.md +++ b/translations/es-ES/data/reusables/actions/enterprise-hardware-considerations.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} requiere recursos adicionales de memoria y de CPU cuando se habilitan las {% data variables.product.prodname_actions %}. Antes de habilitar las {% data variables.product.prodname_actions %}, revisa las "Consideraciones de hardware" para tu plataforma en la sección "[Configuar una instancia de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" y asegúrate de que cumplas con los requisitos mínimos para las características que quieres habilitar en {% data variables.product.product_location %}. +If you {% if currentVersion == "enterprise-server@2.22" %} configured the beta of{% else %} configure{% endif %} {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, we recommend that you provision additional CPU and memory resources. The additional resources you need to provision depend on the number of workflows your users run concurrently, and the overall levels of activity for your instance. 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 ee3b8dc80a..3962608417 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 @@ -1,7 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Nota:** Si habilitas la {% data variables.product.prodname_GH_advanced_security %}, las personas que hagan confirmaciones en estos repositorios utilizarán plazas de tu licencia de {% data variables.product.prodname_GH_advanced_security %}. +**Nota:** Si habilitas la {% data variables.product.prodname_GH_advanced_security %}, las personas que hagan confirmaciones en estos repositorios utilizarán plazas de tu licencia de {% data variables.product.prodname_GH_advanced_security %}. This option controls access to all {% data variables.product.prodname_advanced_security %} features including {% if currentVersion == "free-pro-team@latest" %}dependency review,{% endif %} {% data variables.product.prodname_code_scanning %}, and {% data variables.product.prodname_secret_scanning %}. {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/code-scanning/enabling-options.md b/translations/es-ES/data/reusables/code-scanning/enabling-options.md index 0bf07efd6b..26f24b47f8 100644 --- a/translations/es-ES/data/reusables/code-scanning/enabling-options.md +++ b/translations/es-ES/data/reusables/code-scanning/enabling-options.md @@ -15,7 +15,7 @@ - Utilizar {% data variables.product.prodname_actions %} (consulta la sección "Habilitar el {% data variables.product.prodname_code_scanning %} utilizando acciones") o utilizar el {% data variables.product.prodname_codeql_runner %} en un sistema de integración continua (IC) de terceros (consulta la sección "Ejecutar el escaneo de código en tu sistema de IC"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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"). @@ -25,7 +25,7 @@ - Utilizar {% data variables.product.prodname_actions %} (consulta la sección "Habilitar el {% data variables.product.prodname_code_scanning %}utilizando acciones") o generarlas externamente y cargarlas a {% data variables.product.product_name %} (consulta la sección "Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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 %}"). 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 90af38cccc..5de9816f29 100644 --- a/translations/es-ES/data/reusables/dependabot/supported-package-managers.md +++ b/translations/es-ES/data/reusables/dependabot/supported-package-managers.md @@ -8,7 +8,7 @@ The following table shows, for each package manager: | -------------------------- | ---------------- | ------------------------- |:--------------------:|:--------------------------:| | Bundler | `bundler` | v1 | | **✓** | | Cargo | `cargo` | v1 | **✓** | | -| Composer | `composer` | v1,v2 | **✓** | | +| Composer | `composer` | v1, v2 | **✓** | | | Docker | `docker` | v1 | **✓** | | | Elixir | `mix` | v1 | **✓** | | | Elm | `elm` | v0.18, v0.19 | **✓** | | @@ -17,7 +17,7 @@ The following table shows, for each package manager: | Go modules | `gomod` | v1 | **✓** | **✓** | | Gradle | `gradle` | see (A) below | **✓** | | | Maven | `maven` | see (B) below | **✓** | | -| npm | `npm` | v6 | **✓** | | +| npm | `npm` | v6, v7 | **✓** | | | NuGet | `nuget` | <= 4.8.
see (C) below | **✓** | | | pip | `pip` | v20 | | | | pipenv | `pip` | <= 2018.11.26 | | | diff --git a/translations/es-ES/data/reusables/desktop/choose-clone-repository.md b/translations/es-ES/data/reusables/desktop/choose-clone-repository.md index 60d3ab7a9c..4737b45aa1 100644 --- a/translations/es-ES/data/reusables/desktop/choose-clone-repository.md +++ b/translations/es-ES/data/reusables/desktop/choose-clone-repository.md @@ -1 +1,13 @@ 1. En el menú **File (Archivo)** haz clic en **Clone Repository (Clonar repositorio)**. + + {% mac %} + + ![Clonar opción de menú en la aplicación Mac](/assets/images/help/desktop/clone-file-menu-mac.png) + + {% endmac %} + + {% windows %} + + ![Opción Clone menu (Clonar menú) en la app de Windows](/assets/images/help/desktop/clone-file-menu-windows.png) + + {% endwindows %} diff --git a/translations/es-ES/data/reusables/desktop/choose-local-path.md b/translations/es-ES/data/reusables/desktop/choose-local-path.md new file mode 100644 index 0000000000..be6a8fe784 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/choose-local-path.md @@ -0,0 +1,13 @@ +1. Click **Choose...** and navigate to a local path where you want to clone the repository. + + {% mac %} + + ![El botón Choose (Elegir)](/assets/images/help/desktop/clone-choose-button-mac.png) + + {% endmac %} + + {% windows %} + + ![El botón Choose (Elegir)](/assets/images/help/desktop/clone-choose-button-win.png) + + {% endwindows %} diff --git a/translations/es-ES/data/reusables/desktop/click-clone.md b/translations/es-ES/data/reusables/desktop/click-clone.md new file mode 100644 index 0000000000..efc22ac7fa --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/click-clone.md @@ -0,0 +1,14 @@ +1. Haz clic en **Clone**. + + {% mac %} + + ![El botón Clone (Clonar)](/assets/images/help/desktop/clone-button-mac.png) + + {% endmac %} + + {% windows %} + + ![El botón Clone (Clonar)](/assets/images/help/desktop/clone-button-win.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/es-ES/data/reusables/desktop/cloning-location-tab.md b/translations/es-ES/data/reusables/desktop/cloning-location-tab.md index c8253e6267..372de5b4f3 100644 --- a/translations/es-ES/data/reusables/desktop/cloning-location-tab.md +++ b/translations/es-ES/data/reusables/desktop/cloning-location-tab.md @@ -1 +1,13 @@ 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. + + {% mac %} + + ![Pestañas de ubicación en el menú Clone a repository (Clonar un repositorio)](/assets/images/help/desktop/choose-repository-location-mac.png) + + {% endmac %} + + {% windows %} + + ![Pestañas de ubicación en el menú Clone a repository (Clonar un repositorio)](/assets/images/help/desktop/choose-repository-location-win.png) + + {% endwindows %} diff --git a/translations/es-ES/data/reusables/desktop/cloning-repository-list.md b/translations/es-ES/data/reusables/desktop/cloning-repository-list.md index 98054b13f6..4b35032658 100644 --- a/translations/es-ES/data/reusables/desktop/cloning-repository-list.md +++ b/translations/es-ES/data/reusables/desktop/cloning-repository-list.md @@ -1 +1,14 @@ 1. Elige dentro de la lista el repositorio que deseas clonar. + + + {% mac %} + + ![Clonar una lista de repositorio](/assets/images/help/desktop/clone-a-repository-list-mac.png) + + {% endmac %} + + {% windows %} + + ![Clonar una lista de repositorio](/assets/images/help/desktop/clone-a-repository-list-win.png) + + {% endwindows %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/desktop/fork-type-prompt.md b/translations/es-ES/data/reusables/desktop/fork-type-prompt.md new file mode 100644 index 0000000000..1067dab748 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/fork-type-prompt.md @@ -0,0 +1,42 @@ +1. If you plan to use this fork for contributing to the original upstream repository, click **To contribute to the parent project**. + + {% mac %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/mac-fork-options-prompt.png) + + {% endmac %} + + {% windows %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/windows-fork-options-prompt.png) + + {% endwindows %} + +2. If you plan to use this fork for a project not connected to the upstream, click **For my own purposes**. + + {% mac %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/mac-fork-own-purposes.png) + + {% endmac %} + + {% windows %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/windows-fork-own-purposes.png) + + {% endwindows %} + +3. Click **Continue**. + + {% mac %} + + ![The continue button](/assets/images/help/desktop/mac-forking-continue.png) + + {% endmac %} + + {% windows %} + + ![The continue button](/assets/images/help/desktop/windows-forking-continue.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/es-ES/data/reusables/desktop/open-repository-settings.md b/translations/es-ES/data/reusables/desktop/open-repository-settings.md new file mode 100644 index 0000000000..5e298edc85 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/open-repository-settings.md @@ -0,0 +1,14 @@ +1. Open the **Repository** menu, then click **Repository settings...**. + + {% mac %} + + ![Repository settings menu option in the Mac app](/assets/images/help/desktop/mac-repository-settings.png) + + {% endmac %} + + {% windows %} + + ![Repository settings menu option in the Windows app](/assets/images/help/desktop/windows-repository-settings.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/es-ES/data/reusables/desktop/select-fork-behavior.md b/translations/es-ES/data/reusables/desktop/select-fork-behavior.md new file mode 100644 index 0000000000..fcc7077cd1 --- /dev/null +++ b/translations/es-ES/data/reusables/desktop/select-fork-behavior.md @@ -0,0 +1,28 @@ +1. Click **Fork behavior**, then select how you want to use the fork. + + {% mac %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-menu-contribute.png) + + {% endmac %} + + {% windows %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-menu-contribute.png) + + {% endwindows %} + +2. Haz clic en **Save ** (guardar). + + {% mac %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-save.png) + + {% endmac %} + + {% windows %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-save.png) + + {% endwindows %} + \ No newline at end of file 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 new file mode 100644 index 0000000000..63fa9473e7 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md @@ -0,0 +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 including with your account. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/payment-information-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/payment-information-tab.md new file mode 100644 index 0000000000..4de0966ad7 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/payment-information-tab.md @@ -0,0 +1 @@ +1. Under "Billing", click **Payment information**. diff --git a/translations/es-ES/data/reusables/enterprise_installation/about-adjusting-resources.md b/translations/es-ES/data/reusables/enterprise_installation/about-adjusting-resources.md new file mode 100644 index 0000000000..eb0ee5ca10 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise_installation/about-adjusting-resources.md @@ -0,0 +1 @@ +Para obtener más información sobre el ajuste de recursos para una instancia existente, consulta las secciones "[Incrementar la capacidad de almacenamiento](/enterprise/admin/installation/increasing-storage-capacity)" e "[Incrementar los recursos de memoria o de CPU](/enterprise/admin/installation/increasing-cpu-or-memory-resources)". diff --git a/translations/es-ES/data/reusables/enterprise_installation/aws-supported-instance-types.md b/translations/es-ES/data/reusables/enterprise_installation/aws-supported-instance-types.md index 376fb98ffc..963de76a9f 100644 --- a/translations/es-ES/data/reusables/enterprise_installation/aws-supported-instance-types.md +++ b/translations/es-ES/data/reusables/enterprise_installation/aws-supported-instance-types.md @@ -1,37 +1,13 @@ -{% 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/). +{% data variables.product.prodname_ghe_server %} is supported on the following EC2 instance sizes. 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{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} - -| Tipo de instancia EC2 | Modelo | -| --------------------- | ------------------------ | -| X1 | x1.16xlarge, x1.32xlarge | +| Type | Size | +|:---- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | +| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | +| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | +| M3 | m3.xlarge, m3.2xlarge | +| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | +| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | +| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | +| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} +| X1 | x1.16xlarge, x1.32xlarge | diff --git a/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 84e8d11c99..f09e09b020 100644 --- a/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/es-ES/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,6 +1,5 @@ - [Requisitos mínimos](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} -- [Características beta en {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} -- [Caracteristicas opcionales](#optional-features){% endif %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %} - [Almacenamiento](#storage) - [CPU y memoria](#cpu-and-memory) @@ -8,20 +7,7 @@ Te recomendamos utilizar configuraciones de hardware diferentes dependiendo de la cantidad de licencias de usuario que tengas para {% data variables.product.product_location %}. Si aprovisionaste más recursos que los de los requisitos mínimos, tu instancia funcionrá y escalará mejor. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} Si habilitas {% if currentVersion == "enterprise-server@2.22" %}el beta para {% endif %}{% data variables.product.prodname_actions %}, revisa los siguientes requisitos y recomendaciones. - -- Debes configurar por lo menos un ejecutor para los flujos de trabajo de {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners)." -- Debes configurar un almacenamiento externo de blobs. 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)". -- Puede que necesites configurar recursos adicionales de memoria y CPU. Los recursos adicionales que necesitas para aprovisionar a las {% data variables.product.prodname_actions %} dependen de la cantidad de flujos de trabajo que tus usuarios ejecutan simultáneamente y de los niveles de actividad de los usuarios, automatizaciones e integraciones. - - | Jobs máximos por minuto | vCPU adicionales | Memoria adicional | - |:----------------------- | ----------------:| -----------------:| - | Pruebas ligeras | 4 | 30.5 GB | - | 25 | 8 | 61 GB | - | 35 | 16 | 122 GB | - | 100 | 32 | 244 GB | - -{% endif %} +{% data reusables.enterprise_installation.hardware-rec-table %} #### Almacenamiento @@ -31,7 +17,7 @@ Tu instancia requiere un disco de datos persistentes independiente del disco ra {% if currentVersion ver_gt "enterprise-server@2.21" %} -Si habilitas{% if currentVersion == "enterprise-server@2.22" %} el beta de {% endif %} {% data variables.product.prodname_actions %}, necesitarás configurar un almacenamiento de blobs externo. 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)". +To configure{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you must provide external blob storage. 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)". {% endif %} @@ -39,7 +25,7 @@ Puedes redimensionar el disco raíz de tu instancia si creas una instancia nueva #### CPU y memoria -{% data variables.product.prodname_ghe_server %} requiere más recursos de memoria y de CPU dependiendo de los niveles de actividad de los usuarios, automatizaciones e integraciones. +The CPU and memory resources that {% data variables.product.prodname_ghe_server %} requires depend on the levels of activity for users, automations, and integrations. {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data reusables.actions.enterprise-hardware-considerations %}{% endif %} {% data reusables.enterprise_installation.increasing-cpus-req %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md index 0664207a3d..b7749e6b3f 100644 --- a/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,20 +1,20 @@ -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Nota**: Si habilitas las {% data variables.product.prodname_actions %} o el {% data variables.product.prodname_registry %}, tu instancia requerirá de recursos de hardware adicionales. Los requisitos mínimos para una instancia con características {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}opcionales{% endif %} habilitadas se encuentran en **negritas** en la siguiente tabla. Para obtener más información, consulta la sección "{% if currentVersion == "enterprise-server@2.22" %}[Características beta en {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Características opcionales](#optional-features){% endif %}". +**Note**: If you joined the beta for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} and enabled the features, your instance requires additional hardware resources. Los requisitos mínimos para una instancia con características beta habilitadas se muestran en **negritas** en la siguiente tabla. Para obtener más informaci´n, consulta la sección "[Características beta en {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)". {% endnote %} {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -| Licencias de usuario | vCPU | Memoria | Almacenamiento conectado | Almacenamiento raíz | -|:---------------------------------------- | -------------------------------------------:| ---------------------------------------------------:| ---------------------------------------------------:| -------------------:| -| Prueba, Demo o 10 usuarios no frecuentes | 2
o [**4**](#optional-features) | 16 GB
o [**32 GB**](#optional-features) | 100 GB
o [**150 GB**](#optional-features) | 200 GB | -| 10-3000 | 4
o [**8**](#optional-features) | 32 GB
o [**48 GB**](#optional-features) | 250 GB
o [**300 GB**](#optional-features) | 200 GB | -| 3000-5000 | 8
o [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | -| 5000-8000 | 12
o [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | -| 8000-10000+ | 16
o [**20**](#optional-features) | 128 GB
o [**160 GB**](#optional-features) | 1000 GB | 200 GB | +| Licencias de usuario | vCPU | Memoria | Almacenamiento conectado | Almacenamiento raíz | +|:---------------------------------------- | ----:| -------:| ------------------------:| -------------------:| +| Prueba, Demo o 10 usuarios no frecuentes | 4 | 32 GB | 150 GB | 200 GB | +| 10-3000 | 8 | 48 GB | 300 GB | 200 GB | +| 3000-5000 | 12 | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 16 | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 20 | 160 GB | 1000 GB | 200 GB | {% else %} @@ -28,22 +28,20 @@ {% endif %} -Para obtener más información sobre el ajuste de recursos para una instancia existente, consulta las secciones "[Incrementar la capacidad de almacenamiento](/enterprise/admin/installation/increasing-storage-capacity)" e "[Incrementar los recursos de memoria o de CPU](/enterprise/admin/installation/increasing-cpu-or-memory-resources)". +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +If you plan to configure {% data variables.product.prodname_actions %} for your instance, you should provision additional resources. You must also configure at least one self-hosted runner to execute workflows. 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)". + +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} #### Características beta en {% data variables.product.prodname_ghe_server %} 2.22 -Puedes registrarte para las características del beta disponibles en {% data variables.product.prodname_ghe_server %} 2.22 tales como las {% data variables.product.prodname_actions %}, el {% data variables.product.prodname_registry %}, y el {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta las [notas de lanzamiento para la serie 2.22](https://enterprise.github.com/releases/series/2.22#release-2.22.0) en el sitio web de {% data variables.product.prodname_enterprise %}. +{% data variables.product.prodname_ghe_server %} 2.22 offered features in beta, such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [{% data variables.product.prodname_ghe_server %} 2.22 release notes](/enterprise-server@2.22/admin/release-notes#2.22.0). -Si habilitas las características beta para {% data variables.product.prodname_ghe_server %} 2.22, tu instancia requerirá de recursos de hardware adicionales. Para obtener más información, consulta la sección "[Requisitos mínimos](#minimum-requirements)". - -{% elsif currentVersion ver_gt "enterprise-server@2.22" %} - -#### Características opcionales - -Puedes habilitar las características opcionales para {% data variables.product.prodname_ghe_server %}, tales como las {% data variables.product.prodname_actions %} y el {% data variables.product.prodname_registry %}. 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)" o "[Iniciar con el {% data variables.product.prodname_registry %} para tu empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". - -Si habilitas las características opcionales, tu instancia requerirá recursos de hardware adicionales. Para obtener más información, consulta la sección "[Requisitos mínimos](#minimum-requirements)". +If you enabled beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. Para obtener más información, consulta la sección "[Requisitos mínimos](#minimum-requirements)". {% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/auto-merge.md b/translations/es-ES/data/reusables/gated-features/auto-merge.md index d246a02f8c..acfb4dddff 100644 --- a/translations/es-ES/data/reusables/gated-features/auto-merge.md +++ b/translations/es-ES/data/reusables/gated-features/auto-merge.md @@ -1 +1 @@ -La fusión automática para las solicitudes de cambios se encuentra disponible 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 %}, y {% data variables.product.prodname_ghe_cloud %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} \ No newline at end of file +Auto-merge for pull requests 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 %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/code-scanning.md b/translations/es-ES/data/reusables/gated-features/code-scanning.md index bb9250bab9..35598cce54 100644 --- a/translations/es-ES/data/reusables/gated-features/code-scanning.md +++ b/translations/es-ES/data/reusables/gated-features/code-scanning.md @@ -1 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" %}El {% data variables.product.prodname_code_scanning_capc %} se encuentra disponible para todos los repositorios públicos y para aquellos privados que pertenezcan a organizaciones en donde se ha habilitado la {% data variables.product.prodname_GH_advanced_security %}.{% else %}El{% data variables.product.prodname_code_scanning_capc %} se encuentra disponible si tienes una licencia para la {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled. +{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository. +{%- else %} +{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} 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 bfa353f5d3..df3e8896c6 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 @@ -1,8 +1,8 @@ -| 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 Big Sur 11.0 | `macos-11.0` | -| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | +| Entorno virtual | Etiqueta de flujo de trabajo YAML | +| -------------------- | -------------------------------------------- | +| Windows Server 2019 | `windows-latest` o `windows-2019` | +| Ubuntu 20.04 | `ubuntu-latest` (see note) or `ubuntu-20.04` | +| Ubuntu 18.04 | `ubuntu-latest` (see note) or `ubuntu-18.04` | +| Ubuntu 16.04 | `ubuntu-16.04` | +| macOS Big Sur 11.0 | `macos-11.0` | +| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | diff --git a/translations/es-ES/data/reusables/github-actions/ubuntu-runner-preview.md b/translations/es-ES/data/reusables/github-actions/ubuntu-runner-preview.md index 16447a14e6..6eb91edc13 100644 --- a/translations/es-ES/data/reusables/github-actions/ubuntu-runner-preview.md +++ b/translations/es-ES/data/reusables/github-actions/ubuntu-runner-preview.md @@ -1,5 +1,5 @@ {% 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. +**Note:** The `ubuntu-latest` label is currently being migrated from the Ubuntu 18.04 virtual environment to Ubuntu 20.04. Specifying the `ubuntu-latest` label during the migration might use either virtual environment. To explicitly use Ubuntu 20.04 or Ubuntu 18.04, specify `ubuntu-20.04` or `ubuntu-18.04`. When the migration is complete, `ubuntu-latest` will use the Ubuntu 20.04 virtual environment. For more information about the migration, see "[Ubuntu-latest workflows will use Ubuntu-20.04](https://github.com/actions/virtual-environments/issues/1816)." {% endnote %} diff --git a/translations/es-ES/data/reusables/organizations/organizations_include.md b/translations/es-ES/data/reusables/organizations/organizations_include.md index d82cab580e..6ddd03fb74 100644 --- a/translations/es-ES/data/reusables/organizations/organizations_include.md +++ b/translations/es-ES/data/reusables/organizations/organizations_include.md @@ -6,3 +6,4 @@ Las organizaciones incluyen: - [Los elementos anidados que reflejan la estructura de tu grupo o compañía](/articles/about-teams) con permisos de acceso y menciones en cascada{% if currentVersion != "github-ae@latest" %} - 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 de [requerir que todos los miembros de la organización utilicen autenticación bifactorial](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} +{% if currentVersion == "free-pro-team@latest" %}- The option to purchase a license for {% data variables.product.prodname_GH_advanced_security %} and use the features on private repositories. {% data reusables.advanced-security.more-info-ghas %}{% endif %} diff --git a/translations/es-ES/data/reusables/pages/new-or-existing-repo.md b/translations/es-ES/data/reusables/pages/new-or-existing-repo.md index e4df9329e3..929c47d6c4 100644 --- a/translations/es-ES/data/reusables/pages/new-or-existing-repo.md +++ b/translations/es-ES/data/reusables/pages/new-or-existing-repo.md @@ -1,3 +1,5 @@ Si tu sitio es un proyecto independiente, puedes crear un repositorio nuevo para almacenar el código fuente del mismo. Si tu sitio se asocia con un proyecto existente, puedes agregar el código fuente{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}al repositorio de ese proyecto en una carpeta de `/docs` en la rama predeterminada o en una rama diferente.{% else %}para tu sitio a una rama de `gh-pages` o una carpeta de `docs` en la rama `master` en el repositorio de ese proyecto.{% endif %} Por ejemplo, si creas un sitio para publicar documentos para un proyecto que ya está en {% data variables.product.product_name %}, tal vez quieras almacenar el código fuente para este sitio en el mismo repositorio del proyecto. +{% if currentVersion == "free-pro-team@latest" %}If the account that owns the repository uses {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_free_team %}, the repository must be public.{% endif %} + 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-ES/data/reusables/pull_requests/you-can-auto-merge.md b/translations/es-ES/data/reusables/pull_requests/you-can-auto-merge.md index 9c4ceacd24..479eb377fd 100644 --- a/translations/es-ES/data/reusables/pull_requests/you-can-auto-merge.md +++ b/translations/es-ES/data/reusables/pull_requests/you-can-auto-merge.md @@ -1,3 +1,3 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Puedes configurar una solicitud de cambios para que se fusione automáticamente cuando se cumplan todos los requisitos de fusión. Para obtener más información, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)". -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md index d704b5188f..48915d1e61 100644 --- a/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| Clave | Type | Descripción | -| -------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `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ó. | +| Clave | Type | Descripción | +| -------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción que se realizó. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `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ó. | diff --git a/translations/es-ES/data/variables/action_code_examples.yml b/translations/es-ES/data/variables/action_code_examples.yml index b44db3d5ea..e7f20e4901 100644 --- a/translations/es-ES/data/variables/action_code_examples.yml +++ b/translations/es-ES/data/variables/action_code_examples.yml @@ -24,7 +24,7 @@ - etiquetas - title: Agregar lanzamientos a GitHub - description: Publicar los lanzamientos de GitHub en una acción + description: Publish GitHub releases in an action languages: 'Dockerfile, Shell' href: elgohr/Github-Release-Action tags: @@ -32,7 +32,7 @@ - publicar - title: Publicar una imagen de docker en Dockerhub - description: Una acción de GitHub que se utiliza para crear y publicar imágenes de Docker + description: A GitHub Action used to build and publish Docker images languages: 'Dockerfile, Shell' href: elgohr/Publish-Docker-Github-Action tags: @@ -123,7 +123,7 @@ - publicar - title: Etiqueta tus solicitudes de cambios auto-mágicamente (utilizando archivos confirmados) - description: Acción de Github para etiquetar tus solicitudes de cambios auto-mágicamente (utilizando archivos confirmados) + description: GitHub action to label your pull requests auto-magically (using committed files) languages: 'TypeScript, Dockerfile, JavaScript' href: Decathlon/pull-request-labeler-action tags: @@ -132,7 +132,7 @@ - etiquetas - title: Agregar una etiqueta a tus solicitudes de cambios en nombre del equipo autor - description: Acción de GitHub para etiquetar tus solicitudes de cambios con base en el nombre del autor + description: GitHub action to label your pull requests based on the author name languages: 'TypeScript, JavaScript' href: JulienKode/team-labeler-action tags: diff --git a/translations/es-ES/data/variables/product.yml b/translations/es-ES/data/variables/product.yml index c55d444783..5876546507 100644 --- a/translations/es-ES/data/variables/product.yml +++ b/translations/es-ES/data/variables/product.yml @@ -147,10 +147,10 @@ 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://docs.github.com/rest{% elsif enterpriseServerVersions contains currentVersion %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif currentVersion == "github-ae@latest" %}https://docs.github.com/github-ae@latest/rest{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% endif %} #Use this inside command-line code blocks #Enterprise OAuth paths that don't include "/graphql" or "/api/v3" oauth_host_code: >- @@ -159,10 +159,10 @@ device_authorization_url: >- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}[`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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/graphql{% endif %} 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 feeb35852a..41884cf3cc 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 @@ -63,7 +63,7 @@ type: overview {% data reusables.github-actions.usage-api-requests %} - **ジョブマトリックス** - {% data reusables.github-actions.usage-matrix-limits %} -### セルフホストランナーをサポートするオペレーティングシステム +### Supported architectures and operating systems for self-hosted runners セルフホストランナーアプリケーション用には、以下のオペレーティングシステムがサポートされています。 @@ -92,17 +92,25 @@ type: overview - macOS 10.13 (High Sierra)以降 +#### Architectures + +The following processor architectures are supported for the self-hosted runner application. + +- `x64` - Linux, macOS, Windows. +- `ARM64` - Linux only. +- `ARM32` - Linux only. + {% if enterpriseServerVersions contains currentVersion %} ### セルフホストランナーと{% data variables.product.prodname_dotcom %}との通信 -{% data variables.product.prodname_ghe_server %}とあわせて{% data variables.product.prodname_dotcom_the_website %}からアクションを使う場合、あるいはインターネットアクセスのないセルフホストランナーで`actions/setup-LANGUAGE`アクションを使う場合には、多少の追加設定が必要になるかもしれません。 詳しい情報については「[{% data variables.product.prodname_dotcom_the_website %}からのアクションへのアクセスの管理](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)」を参照し、{% data variables.product.prodname_enterprise %}のサイト管理者に連絡してください。 +そのマシンが{% data variables.product.prodname_actions %}と通信できる。 詳しい情報については「[{% data variables.product.prodname_dotcom_the_website %}からのアクションへのアクセスの管理](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)」を参照し、{% data variables.product.prodname_enterprise %}のサイト管理者に連絡してください。 {% endif %} ### セルフホストランナーと{% data variables.product.product_name %}との通信 -セルフホストランナーは{% data variables.product.product_name %}をポーリングして、アプリケーションのアップデートを取得し、処理のためにジョブがキューイングされていないかチェックします。 セルフホストランナーはHTTPSの_ロングポーリング_を使います。これは{% data variables.product.product_name %}に対して50秒間接続を開き、レスポンスがなければタイムアウトして新しいロングポーリングを生成します。 アプリケーションは、{% data variables.product.prodname_actions %}ジョブを受け付けて実行するためにマシン上で動作していなければなりません。 +The self-hosted runner polls {% data variables.product.prodname_dotcom %} to retrieve application updates and to check if any jobs are queued for processing. The self-hosted runner uses a HTTPS _long poll_ that opens a connection to {% data variables.product.prodname_dotcom %} for 50 seconds, and if no response is received, it then times out and creates a new long poll. アプリケーションは、{% data variables.product.prodname_actions %}ジョブを受け付けて実行するためにマシン上で動作していなければなりません。 {% if currentVersion == "free-pro-team@latest" %} 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 2d046fdcb5..116eaa7461 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 @@ -29,7 +29,7 @@ type: tutorial * `self-hosted`: セルフホストランナーに適用されるデフォルトのラベル。 * `linux`、`windows`、`macOS`: オペレーティングシステムに基づいて適用されます。 -* `x86`、`x64`、`ARM`、`ARM64`: ハードウェアアーキテクチャに基づいて適用されます。 +* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. ワークフローのYAMLを使って、これらのラベルの組み合わせに対してジョブを送信できます。 この例では、3つのラベルすべてにマッチするセルフホストランナーが、ジョブを実行する資格を持つことになります。 diff --git a/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md index eb961ffa02..6eab097d46 100644 --- a/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md @@ -41,12 +41,17 @@ Windowsの仮想マシンは、ユーザアカウント制御（UAC）が無効 ### サポートされているランナーとハードウェアリソース -各仮想マシンで、同一のハードウェアリソースを使用できます。 +Hardware specification for Windows and Linux virtual machines: - 2コアCPU - 7 GBのRAMメモリー - 14 GBのSSDディスク容量 +Hardware specification for macOS virtual machines: +- 3コアCPU +- 14 GBのRAMメモリー +- 14 GBのSSDディスク容量 + {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} @@ -71,9 +76,13 @@ Windowsの仮想マシンは、ユーザアカウント制御（UAC）が無効 {% data variables.product.prodname_dotcom %}ホストランナーには、オペレーティングシステムのデフォルトの組み込みツールに加え、上のリファレンスのリスト内のパッケージにが含まれています。 たとえば、Ubuntu及びmacOSのランナーには、`grep`、`find`、`which`やその他のデフォルトのツールが含まれています。 -ワークフローログには、ランナーにプリインストールされているツールへのリンクが含まれています。 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。 +Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will tell you the the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -リクエストしたいツールがある場合、[actions/virtual-environments](https://github.com/actions/virtual-environments) で Issue を開いてください。 +We recommend using actions to interact with the software installed on runners. This approach has several benefits: +- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters +- It ensures the tool versions used in your workflow will remain the same regardless of software updates + +リクエストしたいツールがある場合、[actions/virtual-environments](https://github.com/actions/virtual-environments) で Issue を開いてください。 This repository also contains announcements about all major software updates on runners. ### IP アドレス diff --git a/translations/ja-JP/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/ja-JP/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index 95fec3e63c..31f20fa564 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/ja-JP/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -73,7 +73,7 @@ If the server on which you are running {% endif %} #### Enabling code scanning for individual repositories -After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. デフォルトの {% data variables.product.prodname_code_scanning %} ワークフローは、`on.push` イベントを使用して、ワークフローファイルを含むブランチへのプッシュごとにコードスキャンをトリガーします。 +After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." ### {% data variables.product.prodname_codeql_runner %} を使用して {% data variables.product.prodname_code_scanning %} を実行する 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 %}. diff --git a/translations/ja-JP/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index 13ad91e0ff..d0493ffa3c 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md @@ -20,7 +20,7 @@ For encryption in transit, {% data variables.product.product_name %} uses Transp The key that you provide is stored in a hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages. -To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and delete your encryption key. Note that deleting your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation. +To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation. ### Adding or updating an encryption key @@ -48,24 +48,24 @@ Your 2048 bit RSA private key should be in PEM format, for example in a file cal curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` -### Deleting your encryption key +### Disabling your encryption key -To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by deleting your encryption key. +To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled. -To unfreeze your enterprise after you've deleted your encryption key, contact support. 詳しい情報については、「[{% data variables.contact.enterprise_support %} について](/admin/enterprise-support/about-github-enterprise-support)」を参照してください。 - -1. To delete your key and disable encryption at rest, use the `DELETE /enterprise/encryption` endpoint. +1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently. ```shell curl -X DELETE http(s)://hostname/api/v3/enterprise/encryption ``` -2. Optionally, check the status of the delete operation. +2. Optionally, check the status of the delete operation. It takes approximately ten minutes to disable encryption at rest. ```shell curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` +To unfreeze your enterprise after you've disabled your encryption key, contact support. 詳しい情報については、「[{% data variables.contact.enterprise_support %} について](/admin/enterprise-support/about-github-enterprise-support)」を参照してください。 + ### 参考リンク - "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation diff --git a/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md index 0076fc95e0..c3abc1d38c 100644 --- a/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -29,6 +29,26 @@ versions: {% endnote %} +{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %} + +### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later + +Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table. + +| ユーザライセンス | vCPUs | メモリ | アタッチされたストレージ | ルートストレージ | +|:---------------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| --------:| +| トライアル、デモ、あるいは10人の軽量ユーザ | **4**
_Up from 2_ | **32 GB**
_Up from 16 GB_ | **150 GB**
_Up from 100 GB_ | 200 GB | +| 10-3000 | **8**
_Up from 4_ | **48 GB**
_Up from 32 GB_ | **300 GB**
_Up from 250 GB_ | 200 GB | +| 3000-5000 | **12**
_Up from 8_ | 64 GB | 500 GB | 200 GB | +| 5000-8000 | **16**
_Up from 12_ | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | **20**
_Up from 16_ | **160 GB**
_Up from 128 GB_ | 1000 GB | 200 GB | + +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% endif %} + ### スナップショットの取得 スナップショットは、ある時点での仮想マシン（VM）のチェックポイントです。 アップグレードに失敗した場合にスナップショットからVMを回復できるよう、仮想マシンをアップグレードする前にスナップショットを取っておくことを強くおすすめします。 新しいフィーチャリリースにアップグレードするなら、VM のスナップショットを取らなければなりません。 パッチリリースへのアップグレードをするなら、既存のデータディスクをアタッチできます。 diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md index 785344ee35..dbb7fbf2c6 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -9,13 +9,7 @@ versions: enterprise-server: '>=2.22' --- -{% if currentVersion == "enterprise-server@2.22" %} -{% note %} - -**注釈:** {% data variables.product.prodname_ghe_server %} 2.22 での {% data variables.product.prodname_actions %} サポートは、限定パブリックベータです。 Review the external storage requirements below and [sign up for the beta](https://resources.github.com/beta-signup/). - -{% endnote %} -{% endif %} +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} @@ -23,11 +17,33 @@ versions: この記事では、サイト管理者が {% data variables.product.prodname_actions %} を使用するように {% data variables.product.prodname_ghe_server %} を設定する方法について説明しています。 ハードウェアとソフトウェアの要件、ストレージオプション、セキュリティ管理ポリシーについて説明します。 +{% endif %} + ### ハードウェアについての留意点を確認する +{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %} + +{% note %} + +**Note**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. 詳細は「[{% data variables.product.prodname_ghe_server %} をアップグレードする](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)」を参照してください。 + +{% endnote %} + +{% endif %} + {% data reusables.actions.enterprise-hardware-considerations %} -{% endif %} +For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform. + +- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) +- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) +- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) +- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) +- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) +- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations) +- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations) + +{% data reusables.enterprise_installation.about-adjusting-resources %} ### 外部ストレージの要件 @@ -55,7 +71,7 @@ versions: ### {% data variables.product.prodname_actions %} の有効化 -{% data variables.product.prodname_ghe_server %} 2.22 での {% data variables.product.prodname_actions %} サポートは、限定パブリックベータです。 [Sign up for the beta](https://resources.github.com/beta-signup/). +{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." ### 参考リンク diff --git a/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md index 070837a43b..be42a98cf7 100644 --- a/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/customizing-user-messages-for-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: Customizing user messages for your enterprise +title: Enterprise のユーザメッセージをカスタマイズする redirect_from: - /enterprise/admin/user-management/creating-a-custom-sign-in-message/ - /enterprise/admin/user-management/customizing-user-messages-on-your-instance diff --git a/translations/ja-JP/content/admin/user-management/managing-dormant-users.md b/translations/ja-JP/content/admin/user-management/managing-dormant-users.md index 64ae316381..d833aafcba 100644 --- a/translations/ja-JP/content/admin/user-management/managing-dormant-users.md +++ b/translations/ja-JP/content/admin/user-management/managing-dormant-users.md @@ -5,7 +5,7 @@ redirect_from: - /enterprise/admin/articles/viewing-dormant-users/ - /enterprise/admin/articles/determining-whether-a-user-account-is-dormant/ - /enterprise/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.{% if enterpriseServerVersions contains currentVersion %} You may choose to suspend dormant users to free up user licenses.{% endif %} +intro: ユーザアカウントが少なくとも 1 か月間アクティブになっていない場合、休眠状態であると見なされます。{% if enterpriseServerVersions contains currentVersion %} 休眠ユーザを一時停止してユーザライセンスを解放することができます。{% endif %} versions: enterprise-server: '*' github-ae: '*' @@ -15,7 +15,7 @@ versions: - {% data variables.product.product_name %} へのサインイン。 - Issue やプルリクエストへのコメント。 - リポジトリの作成、削除、Watch、スター付け。 -- Pushing commits.{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +- コミットのプッシュ。{% if currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} - Accessing resources by using a personal access token or SSH key.{% endif %} ### 休眠ユーザの表示 diff --git a/translations/ja-JP/content/admin/user-management/managing-global-webhooks.md b/translations/ja-JP/content/admin/user-management/managing-global-webhooks.md index a328a6486a..22e3f1aa1f 100644 --- a/translations/ja-JP/content/admin/user-management/managing-global-webhooks.md +++ b/translations/ja-JP/content/admin/user-management/managing-global-webhooks.md @@ -1,6 +1,6 @@ --- title: グローバルwebhookの管理 -intro: 'Site administrators can view, add, edit, and delete global webhooks to track events for the enterprise.' +intro: 'サイト管理者は、グローバル webhook を表示、追加、編集、削除して、Enterprise のイベントを追跡できます。' redirect_from: - /enterprise/admin/user-management/about-global-webhooks - /enterprise/admin/user-management/managing-global-webhooks @@ -11,7 +11,7 @@ versions: ### グローバルwebhookについて -You can use global webhooks to automatically monitor, respond to, or enforce rules for user and organization management for your enterprise. たとえば以下のような場合に動作するようにwebhookを設定できます: +グローバル webhook を使用して、Enterprise ユーザおよび Organization 管理のルールを自動的に監視、応答、適用できます。 たとえば以下のような場合に動作するようにwebhookを設定できます: - ユーザアカウントが作成または削除される - An organization is created or deleted - コラボレータがリポジトリに追加、またはリポジトリから削除される diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise.md index ac79e72f25..b402ac0967 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise.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: 'Organizationは企業内で、部署や同様のプロジェクトで作業を行うグループなど、個別のユーザグループを作成する素晴らしい手段です。 {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to users in other organizations, while private repositories are inaccessible to anyone but members of the organization that are granted access.' +intro: 'Organizationは企業内で、部署や同様のプロジェクトで作業を行うグループなど、個別のユーザグループを作成する素晴らしい手段です。 {% if currentVersion == "github-ae@latest" %}内部{% else %} Organization に属するパブリックおよび内部{% endif %}リポジトリは、他の Organization のユーザがアクセスできますが、プライベートリポジトリは、アクセスが許可されている Organization のメンバー以外はアクセスできません。' mapTopic: true versions: enterprise-server: '*' diff --git a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise.md index 4da07ed3b7..6f342de93e 100644 --- a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Managing repositories in your enterprise -intro: 'You can manage the settings available to repository administrators in your enterprise.' +intro: 'Enterprise のリポジトリ管理者向けに利用可能な設定を管理できます。' redirect_from: - /enterprise/admin/user-management/repositories - /enterprise/admin/user-management/managing-repositories-in-your-enterprise diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise.md index 63a373005f..33b2ebe8e0 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Managing users in your enterprise -intro: 'You can audit user activity and manage user settings.' +intro: 'ユーザアクティビティを監査し、ユーザ設定を管理できます。' redirect_from: - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/ - /enterprise/admin/user-management/basic-account-settings diff --git a/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md index eb2a7bf1fb..4e46dea738 100644 --- a/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -131,7 +131,7 @@ curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ #### {% data variables.product.prodname_dotcom_the_website %} で Organization からリポジトリを削除する -After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/reference/repos/#delete-a-repository). 認証のためのアクセストークンが必要になります。 +{% data variables.product.prodname_dotcom_the_website %} Organization のリポジトリをロック解除した後、[リポジトリ削除エンドポイント](/rest/reference/repos/#delete-a-repository)を使用して以前に移行したすべてのリポジトリを削除する必要があります。 認証のためのアクセストークンが必要になります。 ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ https://api.github.com/repos/orgname/repo_name diff --git a/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md b/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md index e05a2bc11f..157ff90346 100644 --- a/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md +++ b/translations/ja-JP/content/admin/user-management/migrating-to-internal-repositories.md @@ -23,7 +23,7 @@ versions: インターナルもしくはプライベートになるパブリックリポジトリに対する匿名Git読み取りアクセスは、無効化されます。 -リポジトリに対する現在のデフォルトの可視性がパブリックであれば、デフォルトはインターナルになります。 現在のデフォルトがプライベートであれば、デフォルトは変更されません。 デフォルトはいつでも変更できます。 For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-the-default-visibility-of-new-repositories-in-your-enterprise)." +リポジトリに対する現在のデフォルトの可視性がパブリックであれば、デフォルトはインターナルになります。 現在のデフォルトがプライベートであれば、デフォルトは変更されません。 デフォルトはいつでも変更できます。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-the-default-visibility-of-new-repositories-in-your-enterprise)」を参照してください。 インスタンスに対するリポジトリの作成ポリシーは、パブリックリポジトリの無効化とプライベート及びインターナルリポジトリの許可に変更されます。 このポリシーはいつでも更新できます。 詳しい情報については「[インスタンスでのリポジトリ作成の制限](/enterprise/admin/user-management/restricting-repository-creation-in-your-instance)」を参照してください。 diff --git a/translations/ja-JP/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md b/translations/ja-JP/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md index 81cc8c7d40..1e015ad802 100644 --- a/translations/ja-JP/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md +++ b/translations/ja-JP/content/admin/user-management/placing-a-legal-hold-on-a-user-or-organization.md @@ -1,6 +1,6 @@ --- title: ユーザあるいはOrganizationへの訴訟ホールドの配置 -intro: 'You can place a legal hold on a user or organization to ensure that repositories they own cannot be permanently removed from your enterprise.' +intro: 'ユーザまたは Organization を法的に保留して、それらが所有するリポジトリを Enterprise から完全に削除できないようにすることができます。' redirect_from: - /enterprise/admin/user-management/placing-a-legal-hold-on-a-user-or-organization versions: diff --git a/translations/ja-JP/content/admin/user-management/preventing-users-from-creating-organizations.md b/translations/ja-JP/content/admin/user-management/preventing-users-from-creating-organizations.md index 9065acc157..61dd7a16bf 100644 --- a/translations/ja-JP/content/admin/user-management/preventing-users-from-creating-organizations.md +++ b/translations/ja-JP/content/admin/user-management/preventing-users-from-creating-organizations.md @@ -4,7 +4,7 @@ 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 -intro: 'You can prevent users from creating organizations in your enterprise.' +intro: 'ユーザが Enterprise 内に Organization を作成できないようにすることができます。' versions: enterprise-server: '*' github-ae: '*' diff --git a/translations/ja-JP/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md b/translations/ja-JP/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md index 3a2f1eb80b..f973e07cc2 100644 --- a/translations/ja-JP/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md +++ b/translations/ja-JP/content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md @@ -7,7 +7,7 @@ versions: enterprise-server: '*' --- -When using LDAP or built-in authentication, two-factor authentication is supported on {% data variables.product.product_location %}. Organizationの管理者は、メンバーに対して2要素認証の有効化を必須とすることができます。 +LDAP またはビルトイン認証を使用している場合、{% data variables.product.product_location %} で 2 要素認証がサポートされます。 Organizationの管理者は、メンバーに対して2要素認証の有効化を必須とすることができます。 {% data reusables.enterprise_user_management.external_auth_disables_2fa %} diff --git a/translations/ja-JP/content/admin/user-management/searching-the-audit-log.md b/translations/ja-JP/content/admin/user-management/searching-the-audit-log.md index f196b1cfca..7f0f80a1bb 100644 --- a/translations/ja-JP/content/admin/user-management/searching-the-audit-log.md +++ b/translations/ja-JP/content/admin/user-management/searching-the-audit-log.md @@ -1,6 +1,6 @@ --- title: Audit log を検索する -intro: 'Site administrators can search an extensive list of audited actions on the enterprise.' +intro: 'サイト管理者は、Enterprise で監査されたアクションの広範なリストを検索できます。' redirect_from: - /enterprise/admin/articles/searching-the-audit-log/ - /enterprise/admin/installation/searching-the-audit-log @@ -19,7 +19,7 @@ AND/ORの論理演算子で区切られた値のペア:1つ以上のキーを使 | `actor_id` | アクションを開始したユーザアカウントの ID | | `actor` | アクションを開始したユーザアカウントの名前 | | `oauth_app_id` | アクションに関連付けられている OAuth アプリケーションの ID | -| `action` | Name of the audited action | +| `action` | 監査されたアクションの名前 | | `user_id` | アクションによって影響を受けたユーザの ID | | `ユーザ` | アクションによって影響を受けたユーザの名前 | | `repo_id` | アクションによって影響を受けたリポジトリの ID （妥当な場合） | @@ -35,7 +35,7 @@ AND/ORの論理演算子で区切られた値のペア:1つ以上のキーを使 `repo:"octocat/Spoon-Knife" AND created_at:[2017-01-01 TO *]` -For a full list of actions, see "[Audited actions](/admin/user-management/audited-actions)." +アクションの完全なリストについては、「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 ### Audit log を検索する diff --git a/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md index 4e5547718b..7c70eaf71b 100644 --- a/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md +++ b/translations/ja-JP/content/admin/user-management/suspending-and-unsuspending-users.md @@ -83,4 +83,4 @@ fatal: The remote end hung up unexpectedly ``` ### 参考リンク -- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file +- 「[ユーザーをサスペンドする](/rest/reference/enterprise-admin#suspend-a-user)」 \ No newline at end of file diff --git a/translations/ja-JP/content/admin/user-management/viewing-push-logs.md b/translations/ja-JP/content/admin/user-management/viewing-push-logs.md index e2d5d6a891..55a1482d54 100644 --- a/translations/ja-JP/content/admin/user-management/viewing-push-logs.md +++ b/translations/ja-JP/content/admin/user-management/viewing-push-logs.md @@ -1,6 +1,6 @@ --- title: プッシュログの表示 -intro: 'Site administrators can view a list of Git push operations for any repository on the enterprise.' +intro: 'サイト管理者は、Enterprise 上の任意のリポジトリに対する Git プッシュ操作の一覧を確認することができます。' redirect_from: - /enterprise/admin/articles/viewing-push-logs/ - /enterprise/admin/installation/viewing-push-logs @@ -22,9 +22,9 @@ versions: ### リポジトリのプッシュログを表示する -1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator. +1. サイト管理者として {% data variables.product.prodname_ghe_server %} にサインインします。 1. リポジトリにアクセスします。 -1. In the upper-right corner of the repository's page, click +1. リポジトリのページの右上隅にある {% octicon "rocket" aria-label="The rocket ship" %} をクリックします。 {% octicon "rocket" aria-label="The rocket ship" %}. ![サイトアドミン設定にアクセスするための宇宙船のアイコン](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% data reusables.enterprise_site_admin_settings.security-tab %} diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md index 1bc222580e..e952158434 100644 --- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md @@ -8,40 +8,40 @@ versions: free-pro-team: '*' --- -### リポジトリのクローン方法 -{% data variables.product.prodname_dotcom %}上のリポジトリは、リモートリポジトリとして存在します。 他の人が所有するパブリックリポジトリをクローンできます。 自分が所有するリポジトリをクローンして、自分のコンピュータ上にローカルコピーを作成し、これら2つの場所の間で同期を行えます。 +### About local repositories +Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer. + +You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. 詳しい情報については、「[ブランチを同期する](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)」を参照してください。 + +When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. 詳しい情報については「[フォークについて](/github/collaborating-with-issues-and-pull-requests/about-forks)」を参照してください。 + +When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)". リポジトリを{% data variables.product.prodname_dotcom %}、または{% data variables.product.prodname_enterprise %}から直接クローンすることもできます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} から {% 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 %} - ![Mac アプリケーション内の [Clone] メニューオプション](/assets/images/help/desktop/clone-file-menu-mac.png) {% data reusables.desktop.cloning-location-tab %} - ![[Clone a repository] メニュー内の [Location] タブ](/assets/images/help/desktop/choose-repository-location-mac.png) {% data reusables.desktop.cloning-repository-list %} - ![リポジトリリストのクローン](/assets/images/help/desktop/clone-a-repository-list-mac.png) -4. [**Choose...**]をクリックし、Finderウインドウを使用してリポジトリをクローンするローカルパスに移動します。 ![Chooseボタン](/assets/images/help/desktop/clone-choose-button-mac.png) -5. **Clone**をクリックします。 ![Cloneボタン](/assets/images/help/desktop/clone-button-mac.png) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} -{% endmac %} - -{% windows %} +### リポジトリをフォークする +If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork. {% data reusables.desktop.choose-clone-repository %} - ![Windows アプリケーション内の [Clone] メニューオプション](/assets/images/help/desktop/clone-file-menu-windows.png) {% data reusables.desktop.cloning-location-tab %} - ![[Clone a repository] メニュー内の [Location] タブ](/assets/images/help/desktop/choose-repository-location-win.png) {% data reusables.desktop.cloning-repository-list %} - ![リポジトリリストのクローン](/assets/images/help/desktop/clone-a-repository-list-win.png) -4. **Choose...**をクリックし、Windows Explorerを使用してリポジトリをクローンするローカルパスに移動します。 ![Chooseボタン](/assets/images/help/desktop/clone-choose-button-win.png) -5. **Clone**をクリックします。 ![Cloneボタン](/assets/images/help/desktop/clone-button-win.png) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} +{% data reusables.desktop.fork-type-prompt %} -{% endwindows %} +### Managing fork behavior +You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}. -### リポジトリのフォーク -書き込みアクセス権がないプロジェクトにコントリビュートするには、{% data variables.product.prodname_desktop %}を使ってそのリポジトリのフォークを作成します。 フォークに対する変更は、オリジナルのリポジトリには影響しません。 フォークに変更をコミットし、そしてオリジナルのリポジトリに対して提案する変更でプルリクエストをオープンできます。 詳しい情報については「[フォークについて](/github/collaborating-with-issues-and-pull-requests/about-forks)」を参照してください。 +{% data reusables.desktop.open-repository-settings %} +{% data reusables.desktop.select-fork-behavior %} -1. 書き込みアクセス権を持っていないリポジトリをクローンし、変更をコミットしようとすると、{% data variables.product.prodname_desktop %}は次の警告を発します。"You don't have write access to **REPOSITORY**." **create a fork（フォークの作成）**をクリックしてください。 ![フォークの作成リンク](/assets/images/help/desktop/create-a-fork.png) -3. **Fork this repository（このリポジトリをフォーク）**をクリックしてください。 ![このリポジトリのフォークボタン](/assets/images/help/desktop/fork-this-repo-button.png) -4. {% data variables.product.prodname_dotcom %}上のフォークを見るには、{% data variables.product.prodname_dotcom %}の右上で自分のプロフィール画像をクリックし、**Your repositories（あなたのリポジトリ）**をクリックしてください。 ![あなたのリポジトリリンク](/assets/images/help/profile/your-repositories.png) +### 参考リンク +- [リモートリポジトリについて](/github/using-git/about-remote-repositories) diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 72f816a53e..83234dd319 100644 --- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -9,7 +9,7 @@ versions: ### {% data variables.product.prodname_desktop %} のタグについて -{% data variables.product.prodname_desktop %} を使用すると、アノテーションされたタグを作成できます。 タグを使用して、リリースのバージョン番号など、リポジトリの履歴内の個々のポイントをマークできます。 リリースタグに関する詳しい情報については、「[リリースについて](/github/administering-a-repository/about-releases)」を参照してください。 +{% data variables.product.prodname_desktop %} を使用すると、アノテーションされたタグを作成できます。 Tags are associated with commits, so you can use a tag to mark an individual point in your repository's history, including a version number for a release. リリースタグに関する詳しい情報については、「[リリースについて](/github/administering-a-repository/about-releases)」を参照してください。 {% data reusables.desktop.tags-push-with-commits %} @@ -44,3 +44,7 @@ versions: {% data reusables.desktop.history-tab %} {% data reusables.desktop.delete-tag %} + +### 参考リンク + +- "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation diff --git a/translations/ja-JP/content/developers/apps/activating-beta-features-for-apps.md b/translations/ja-JP/content/developers/apps/activating-beta-features-for-apps.md index 074c71b427..eaa0fb64b2 100644 --- a/translations/ja-JP/content/developers/apps/activating-beta-features-for-apps.md +++ b/translations/ja-JP/content/developers/apps/activating-beta-features-for-apps.md @@ -3,6 +3,8 @@ title: アプリケーションのベータ版機能を有効化する intro: 'パブリックベータでリリースたれた新しいアプリケーションの機能を、{% data variables.product.prodname_github_apps %} および {% data variables.product.prodname_oauth_app %} でテストできます。' versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% warning %} diff --git a/translations/ja-JP/content/developers/apps/authenticating-with-github-apps.md b/translations/ja-JP/content/developers/apps/authenticating-with-github-apps.md index 9bbb50091a..cfbf0ab027 100644 --- a/translations/ja-JP/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/ja-JP/content/developers/apps/authenticating-with-github-apps.md @@ -110,7 +110,7 @@ $ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github ```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" + "documentation_url": "{% data variables.product.doc_url_pre %}" } ``` diff --git a/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 1104208b10..45f7d6c326 100644 --- a/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ja-JP/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### はじめに -このガイドでは、[Github App](/apps/) と [Checks API](/rest/reference/checks) について紹介します。Checks API は、テストを実行する継続的インテグレーション (CI) サーバーを構築するために使用します。 +This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. CI とは、ソフトウェアの開発においてコードを頻繁に共有リポジトリにコミットする手法のことです。 コードをコミットする頻度が高いほどエラーの発生が早くなり、開発者がエラーの原因を見つけようとしてデバッグする必要性も減ります。 コードの更新が頻繁であれば、ソフトウェア開発チームの他のメンバーによる変更をマージするのも、それだけ容易になります。 コードの記述により多くの時間をかけられるようになり、エラーのデバッグやマージコンフリクトの解決にかける時間が減るので、これは開発者にとって素晴らしいやり方です。 🙌 @@ -49,7 +49,7 @@ Checks API は、新しいコードがリポジトリにプッシュされるた ### 必要な環境 -以下の作業に取りかかる前に、[Github Apps](/apps/)、[webhook](/webhooks)、[Checks API](/rest/reference/checks) を使い慣れていない場合は、ある程度慣れておくとよいでしょう。 [REST API ドキュメント](/rest)には、さらに多くの API が掲載されています。 Checks API は [GraphQL](/graphql) でも使用できますが、このクイックスタートでは REST に焦点を当てます。 詳細については、GraphQL [Checks Suite](/graphql/reference/objects#checksuite) および [Check Run](/graphql/reference/objects#checkrun) オブジェクトを参照してください。 +Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. [REST API ドキュメント](/rest)には、さらに多くの API が掲載されています。 Checks API は [GraphQL](/graphql) でも使用できますが、このクイックスタートでは REST に焦点を当てます。 詳細については、GraphQL [Checks Suite](/graphql/reference/objects#checksuite) および [Check Run](/graphql/reference/objects#checkrun) オブジェクトを参照してください。 [Ruby プログラミング言語](https://www.ruby-lang.org/en/)、[Smee](https://smee.io/) webhook ペイロード配信サービス、GitHub REST API 用の [Octokit.rb Ruby ライブラリ](http://octokit.github.io/octokit.rb/)、および [Sinatra ウェブフレームワーク](http://sinatrarb.com/) を使用して、Checks API CI サーバーアプリケーションを作成します。 @@ -203,7 +203,7 @@ $ ruby template_server.rb ### ステップ 1.4. チェック実行を更新する -`create_check_run` メソッドが実行されると、メソッドは GitHub に新しいチェック実行を作成するよう依頼します。 Github がチェック実行の作成を完了すると、`created` アクションの `check_run` webhook イベントを受信します。 このイベントは、チェックの実行を開始する合図です。 +`create_check_run` メソッドが実行されると、メソッドは GitHub に新しいチェック実行を作成するよう依頼します。 When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. このイベントは、チェックの実行を開始する合図です。 イベントハンドラーを更新し、`created` アクションを待ち受けるようにしましょう。 イベントハンドラーを更新する際、`rerequested` アクションに条件を追加できます。 誰かが [Re-run] ボタンをクリックして GitHub 上で単一のテストを再実行すると、GitHub はアプリケーションに `rerequested` チェック実行イベントを送信します。 チェック実行が `rerequested` の場合、すべてのプロセスを開始し、新しいチェック実行を作成します。 @@ -435,7 +435,7 @@ clone_repository(full_repo_name, repository, head_sha) ### ステップ 2.3. RuboCop を実行する -これでうまくいきました。 リポジトリをクローンし、CI サーバーを使用してチェック実行を作成しようという段階にまで到達しました。 Now you'll get into the nitty gritty details of the [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). +これでうまくいきました。 リポジトリをクローンし、CI サーバーを使用してチェック実行を作成しようという段階にまで到達しました。 それではいよいよ [RuboCop 文法チェッカー](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) と [Checks API アノテーション](/rest/reference/checks#create-a-check-run)の核心に迫ります。 次のコードは、RuboCop を実行し、スタイル コード エラーを JSON フォーマットで保存します。 [前のステップ](#step-22-cloning-the-repository) で追加した`clone_repository` への呼び出しの下と、チェック実行を更新するコードの上に追加して完了です。 @@ -447,7 +447,7 @@ logger.debug @report @output = JSON.parse @report ``` -上記のコードは、リポジトリのディレクトリにある全てのファイルで RuboCop を実行します。 `--format json` のオプションは、文法チェックの結果のコピーをコンピューターで読みとることができるフォーマットで保存する便利な方法です。 See the [RuboCop docs](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) for details and an example of the JSON format. +上記のコードは、リポジトリのディレクトリにある全てのファイルで RuboCop を実行します。 `--format json` のオプションは、文法チェックの結果のコピーをコンピューターで読みとることができるフォーマットで保存する便利な方法です。 JSON フォーマットの詳細および例については、[RuboCop ドキュメント](https://docs.rubocop.org/rubocop/formatters.html#json-formatter)を参照してください。 このコードは RuboCop の結果を `@report` 変数に格納するため、リポジトリのチェックアウトを安全に削除できます。 また、このコードは JSON も解析するため、`@output` 変数を使用して GitHub App のキーと変数に簡単にアクセスできます。 @@ -588,7 +588,7 @@ end `offense_count` が 0 の場合、CI テストは `success` となります。 エラーがある場合、このコードは結果を `neutral` に設定します。これは、コードの文法チェッカーによるエラーを厳格に強制することを防ぐためです。 ただし、文法エラーがある場合にチェックスイートが失敗になるようにしたい場合は、結果を `failure` に変更できます。 -エラーが報告されると、上記のコードは ReboCop レポートの `files` 配列を反復処理します。 コードは各ファイルにおいてファイルパスを抽出し、アノテーションレベルを `notice` に設定します。 You could go even further and set specific warning levels for each type of [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), but to keep things simpler in this quickstart, all errors are set to a level of `notice`. +エラーが報告されると、上記のコードは ReboCop レポートの `files` 配列を反復処理します。 コードは各ファイルにおいてファイルパスを抽出し、アノテーションレベルを `notice` に設定します。 さらに細かく、[RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html) の各タイプに特定の警告レベルを設定することもできますが、このクイックスタートでは簡単さを優先し、すべてのエラーを `notice` のレベルに設定します。 このコードはまた、`offenses` 配列の各エラーを反復処理し、違反の場所とエラー メッセージを収集します。 必要な情報を抽出後、コードは各エラーに対してアノテーションを作成し、それを `annotations` 配列に格納します。 アノテーションは同一行の開始列と終了列のみをサポートしているため、開始行と終了行の値が同じである場合にのみ `annotation` オブジェクトに `start_column` と `end_column` が追加されます。 @@ -718,7 +718,7 @@ $ ruby template_server.rb ここまで来たのはすごいですよ！ 👏 あなたはもう CI テストを作成しました。 このセクションでは、もう 1 つの機能を追加します。RuboCop を使用して、見つけたエラーを自動的に修正するために使用するための機能です。 すでに[前のセクション](#step-25-updating-the-check-run-with-ci-test-results)で、[Fix this] ボタンを追加しました。 ここでは、ユーザが [Fix this] ボタンをクリックしたときにトリガーされる、`requested_action` チェック実行イベントを処理するコードを追加します。 -The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. `--auto-correct` 機能を使用すると、サーバー上のローカルファイルに更新が適用されます。 RuboCop がこの作業をやってのけた後は、その変更を GitHub にプッシュする必要があります。 +RuboCop ツールには、見つけたエラーを自動的に修正する `--auto-correct` コマンドラインオプションの [機能](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) があります。 `--auto-correct` 機能を使用すると、サーバー上のローカルファイルに更新が適用されます。 RuboCop がこの作業をやってのけた後は、その変更を GitHub にプッシュする必要があります。 リポジトリにブッシュするには、アプリケーションに [Repository contents] への書き込み権限が必要です。 この権限については、[ステップ 2.2. リポジトリをクローンする](#step-22-cloning-the-repository)で既に [**Read & write**] に設定しているので、もう準備は整っています。 diff --git a/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md index 9164c407bf..f8c73ab9cb 100644 --- a/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -52,7 +52,7 @@ GitHub Appは[レート制限に対するスライディングルール](/apps/b #### 新しいGitHub Appの登録 -GitHub Appへ切り替えすることを決めたら、[新しいGitHub Appを作成](/apps/building-github-apps/)しなければなりません。 +Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). #### アプリケーションが必要とする権限の決定 @@ -62,7 +62,7 @@ GitHub Appの設定で、アプリケーションがそれぞれの権限の種 #### webhookのサブスクライブ -新しいGitHub Appを作成し、その権限を選択したら、サブスクライブさせたいwebhookイベントを選択できます。 webhookをサブスクライブする方法を学ぶには、「[GitHub Appの権限の編集](/apps/managing-github-apps/editing-a-github-app-s-permissions/)」を参照してください。 +新しいGitHub Appを作成し、その権限を選択したら、サブスクライブさせたいwebhookイベントを選択できます。 See "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. #### 様々な認証方法の理解 diff --git a/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md index e7a5814f24..47e06dbfda 100644 --- a/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/ja-JP/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,7 +42,7 @@ versions: { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" diff --git a/translations/ja-JP/content/developers/apps/suspending-a-github-app-installation.md b/translations/ja-JP/content/developers/apps/suspending-a-github-app-installation.md index 34e856a444..6006f443ef 100644 --- a/translations/ja-JP/content/developers/apps/suspending-a-github-app-installation.md +++ b/translations/ja-JP/content/developers/apps/suspending-a-github-app-installation.md @@ -5,6 +5,8 @@ redirect_from: - /apps/managing-github-apps/suspending-a-github-app-installation versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% note %} diff --git a/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index 99cbf9b735..f1947b7a53 100644 --- a/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -14,7 +14,7 @@ versions: {% warning %} -{% data variables.product.prodname_marketplace %}でGitHub Appを提供している場合、アプリケーションはOAuthの認可フローに従ってユーザを識別しなければなりません。 このフローをサポートするために、個別のOAuth Appをセットアップする必要はありません。 詳しい情報については「[GitHub Appのユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。 +If you offer a {% data variables.product.prodname_github_app %} in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate {% data variables.product.prodname_oauth_app %} to support this flow. See "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endwarning %} @@ -24,7 +24,7 @@ versions: **Complete order and begin installation（注文を完了してインストールを開始）**をクリックすることで、顧客は購入を完了します。 -そうすると、GitHubは[`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhookに`purchased`アクションを付けてアプリケーションに送信します。 +{% data variables.product.product_name %} then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. `marketplace_purchase` webhookから`effective_date`と`marketplace_purchase`を読み取り、顧客が購入したプラン、支払いサイクルの開始時点、次の支払いサイクルの開始時点を判断してください。 @@ -34,27 +34,27 @@ versions: ### ステップ 2. インストール -アプリケーションがGitHub Appなら、GitHubは顧客に対してアプリケーションの購入時にそのアプリケーションがアクセスできるリポジトリの選択を求めます。 そしてGitHubは、顧客が選択したアカウントにそのアプリケーションをインストールし、選択されたリポジトリへのアクセスを許可します。 +If your app is a {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} prompts the customer to select which repositories the app can access when they purchase it. {% data variables.product.product_name %} then installs the app on the account the customer selected and grants access to the selected repositories. -この時点で、GitHub Appの設定で**Setup URL**を指定しているなら、GitHubは顧客をそのURLへリダイレクトさせます。 Setup URLを指定していないなら、GitHub Appの購入を処理することはできません +At this point, if you specified a **Setup URL** in your {% data variables.product.prodname_github_app %} settings, {% data variables.product.product_name %} will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your {% data variables.product.prodname_github_app %}. {% note %} -**ノート:** **Setup URL**はGitHub Appの設定中でオプションとされていますが、アプリケーションを{% data variables.product.prodname_marketplace %}で提供したい場合には必須のフィールドです。 +**Note:** The **Setup URL** is described as optional in {% data variables.product.prodname_github_app %} settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. {% endnote %} -アプリケーションがOAuth Appなら、GitHubはそれをどこにもインストールしません。 その代わりに、GitHubは顧客を[{% data variables.product.prodname_marketplace %}リスト](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls)で指定された**Installation URL**へ顧客をリダイレクトします。 +If your app is an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} does not install it anywhere. Instead, {% data variables.product.product_name %} redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). -顧客がOAuth Appを購入すると、GitHubはその顧客を選択されたURL（Setup URLもしくはInstallation URL）へリダイレクトし、そのURLには顧客が選択した価格プランがクエリパラメータの`marketplace_listing_plan_id`として含まれます。 +When a customer purchases an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. ### ステップ 3. 認可 顧客がアプリケーションを購入したら、顧客をOAuthの認可フローに送らなければなりません。 -* アプリケーションがGitHub Appなら、GitHubが顧客を**Setup URL**にリダイレクトしたらすぐに認可フローを開始してください。 「[GitHub Appのユーザの特定の認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」のステップに従ってください。 +* If your app is a {% data variables.product.prodname_github_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -* アプリケーションがOAuth Appなら、GitHubが顧客を**Installation URL**にリダイレクトしたらすぐに認可フローを開始してください。 「[OAuth Appの認可](/apps/building-oauth-apps/authorizing-oauth-apps/)」のステップに従ってください。 +* If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)." どちらの種類のアプリケーションでも、最初のステップは顧客をhttps://github.com/login/oauth/authorizeにリダイレクトさせることです。 diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md index 36e5d4e463..560a1557ce 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students.md @@ -13,9 +13,9 @@ versions: {% data reusables.education.about-github-education-link %} -{% data variables.product.prodname_dotcom %} アカウントを持つ誰もが、{% data variables.product.prodname_free_user %} での無制限のパブリックおよびプライベートリポジトリで協業できます。 学生は {% data variables.product.prodname_student_pack %} に応募することもできます。これはプロフェッショナルの開発者が使用するツールやサービスへの無料アクセスを提供します。 For more information, see "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). +{% data variables.product.prodname_dotcom %} アカウントを持つ誰もが、{% data variables.product.prodname_free_user %} での無制限のパブリックおよびプライベートリポジトリで協業できます。 学生は {% data variables.product.prodname_student_pack %} に応募することもできます。これはプロフェッショナルの開発者が使用するツールやサービスへの無料アクセスを提供します。 詳しい情報については、「[学生向け開発者パックへの応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)」および [{% data variables.product.prodname_education %}](https://education.github.com/pack) を参照してください。 -あなたが FIRST robotics club のメンバーなら、あなたの指導者はチームが {% data variables.product.prodname_team %} を使って協力し合うことができるよう、教育者割引に応募できます。これによって、無制限のユーザとプライベートリポジトリが無料で提供されます。 For more information, see "[Apply for an educator or researcher discount](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)." +あなたが FIRST robotics club のメンバーなら、あなたの指導者はチームが {% data variables.product.prodname_team %} を使って協力し合うことができるよう、教育者割引に応募できます。これによって、無制限のユーザとプライベートリポジトリが無料で提供されます。 詳しい情報については、 「[教育者割引または研究者割引への応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)」を参照してください。 ### 参考リンク diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md index 071c5d269d..377551ebf3 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education.md @@ -21,4 +21,4 @@ Teachers can manage a course on software development with {% data variables.prod 学生のリーダー及び教師に対するトレーニングプログラムについて詳しく学ぶには、[{% data variables.product.prodname_dotcom %}Campus Experts](https://education.github.com/students/experts)及び[ Campus Advisors](https://education.github.com/teachers/advisors)を参照してください。 -あなたの学校が {% data variables.product.prodname_dotcom %} と {% data variables.product.prodname_education %} スクールとしてパートナーになっていない場合は、個別に {% data variables.product.prodname_dotcom %} の利用の割引を申請できます。 For more information, see "[Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)" or "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)." +あなたの学校が {% data variables.product.prodname_dotcom %} と {% data variables.product.prodname_education %} スクールとしてパートナーになっていない場合は、個別に {% data variables.product.prodname_dotcom %} の利用の割引を申請できます。 詳しい情報については、「[学校の勉強での {% data variables.product.prodname_dotcom %} の利用](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)」または「[クラスや勉強での {% data variables.product.prodname_dotcom %} の利用](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/)」を参照してください。 diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md index e249d17b89..f757a0d253 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -65,4 +65,4 @@ versions: ### 参考リンク - 「[学生開発者パックに応募する](/articles/applying-for-a-student-developer-pack)」 -- "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" +- 「[学生向け開発者パックへの応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)」 diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md index 29af586574..fd5a5ae73f 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -43,4 +43,4 @@ versions: ### 参考リンク -- "[Apply for an educator or researcher discount](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)" +- 「[教育者・研究者割引への応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)」 diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md index d800a839de..a8d2449616 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -16,7 +16,7 @@ Repl.itは、複数の複数のプログラミング言語をサポートする 学生がボタンをクリックして、初めてRepl.itにアクセスする際は、{% data variables.product.product_name %}認証情報でMakeCode Arcadeにサインインする必要があります。 サインインすると、学生はRepl.itで完全に構成された、課題リポジトリのコードが含まれる開発環境にアクセスできます。 -Repl.itでの作業に関する詳しい情報については、[Repl.itクイックスタートガイド](https://docs.repl.it/misc/quick-start#the-repl-environment)を参照してください。 +Repl.itでの作業に関する詳しい情報については、[Repl.itクイックスタートガイド](https://docs.repl.it/repls/quick-start#the-repl-environment)を参照してください。 グループ課題の場合、学生はRepl.it Multiplayerを利用して共同作業を行うことができます。 詳しい情報については、[Repl.it Multiplayer](https://repl.it/site/multiplayer)のウェブサイトを参照してください。 diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md index 66a0ed4547..82fbbfbcf0 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -30,4 +30,4 @@ versions: ### 参考リンク -- "[Explore the benefits of teaching and learning with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" +- 「[{% data variables.product.prodname_education %} で教える・学ぶメリットの探求](/education/teach-and-learn-with-github-education)」 diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md index 782ee6f564..dbf233b9ae 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -1,6 +1,6 @@ --- title: グループ課題の作成 -intro: 'コースに参加している学生のチームのために、共同課題を作成できます。' +intro: 'コースに参加している学生のTeamのために、共同課題を作成できます。' versions: free-pro-team: '*' redirect_from: @@ -90,29 +90,29 @@ redirect_from: #### オンライン統合開発環境 (IDE) を選択する -{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." +{% data reusables.classroom.about-online-ides %}詳しい情報については、「[{% data variables.product.prodname_classroom %} と IDE の統合](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)」を参照してください。 {% data reusables.classroom.assignments-guide-choose-an-online-ide %} {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} -### Providing feedback +### フィードバックを提供する -Optionally, you can automatically grade assignments and create a space for discussing each submission with the team. +必要に応じて、課題を自動的に再生し、各提出物をTeamで議論するための場を作成できます。 -- [Testing assignments automatically](#testing-assignments-automatically) -- [Preventing changes to important files](#preventing-changes-to-important-files) -- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) +- [課題を自動的にテストする](#testing-assignments-automatically) +- [重要なファイルへの変更を防ぐ](#preventing-changes-to-important-files) +- [フィードバックのためにプルリクエストを作成する](#creating-a-pull-request-for-feedback) -#### Testing assignments automatically +#### 課題を自動的にテストする {% data reusables.classroom.assignments-guide-using-autograding %} -#### Preventing changes to important files +#### 重要なファイルへの変更を防ぐ {% data reusables.classroom.assignments-guide-prevent-changes %} -#### Creating a pull request for feedback +#### フィードバックのためにプルリクエストを作成する {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} @@ -120,11 +120,11 @@ Optionally, you can automatically grade assignments and create a space for discu {% data reusables.classroom.assignments-guide-click-create-assignment-button %} -### Inviting students to an assignment +### 学生を課題に招待する {% data reusables.classroom.assignments-guide-invite-students-to-assignment %} -You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} +課題の [**Teams**] タブで、課題に取り組んでいるTeamや課題を提出したTeamを表示できます。 {% data reusables.classroom.assignments-to-prevent-submission %}
Group assignment @@ -132,7 +132,7 @@ You can see the teams that are working on or have submitted an assignment in the ### 次のステップ -- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/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 %}. +- 課題を作成し、学生がTeamを編成した後、TeamメンバーはGitと{% data variables.product.product_name %}の機能を使用して課題を開始できます。 学生はリポジトリのクローン、コミットのプッシュ、ブランチの管理、プルリクエストの作成およびレビュー、マージコンフリクトへの対処、およびIssueの変更に関するディスカッションが可能です。 あなたもTeamも、リポジトリのコミット履歴をレビューできます。 For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/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 %}. - When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md index 728b7bcf1d..aa8496ad6b 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -72,7 +72,7 @@ By default, a new assignment will create an empty repository for each student on #### オンライン統合開発環境 (IDE) を選択する -{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." +{% data reusables.classroom.about-online-ides %}詳しい情報については、「[{% data variables.product.prodname_classroom %} と IDE の統合](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)」を参照してください。 {% data reusables.classroom.assignments-guide-choose-an-online-ide %} @@ -80,19 +80,19 @@ By default, a new assignment will create an empty repository for each student on Optionally, you can automatically grade assignments and create a space for discussing each submission with the student. -- [Testing assignments automatically](#testing-assignments-automatically) -- [Preventing changes to important files](#preventing-changes-to-important-files) -- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) +- [課題を自動的にテストする](#testing-assignments-automatically) +- [重要なファイルへの変更を防ぐ](#preventing-changes-to-important-files) +- [フィードバックのためにプルリクエストを作成する](#creating-a-pull-request-for-feedback) -#### Testing assignments automatically +#### 課題を自動的にテストする {% data reusables.classroom.assignments-guide-using-autograding %} -#### Preventing changes to important files +#### 重要なファイルへの変更を防ぐ {% data reusables.classroom.assignments-guide-prevent-changes %} -#### Creating a pull request for feedback +#### フィードバックのためにプルリクエストを作成する {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} @@ -100,7 +100,7 @@ Optionally, you can automatically grade assignments and create a space for discu {% data reusables.classroom.assignments-guide-click-create-assignment-button %} -### Inviting students to an assignment +### 学生を課題に招待する {% data reusables.classroom.assignments-guide-invite-students-to-assignment %} @@ -112,7 +112,7 @@ You can see whether a student has joined the classroom and accepted or submitted ### 次のステップ -- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." +- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. 学生はリポジトリのクローン、コミットのプッシュ、ブランチの管理、プルリクエストの作成およびレビュー、マージコンフリクトへの対処、およびIssueの変更に関するディスカッションが可能です。 Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." - When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." diff --git a/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md index cccdc21126..b4678c7369 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -3,6 +3,7 @@ title: GitHub Dependabot のバージョンアップデートについて intro: '{% data variables.product.prodname_dependabot %} を使用して、使用するパッケージを最新バージョンに更新しておくことができます。' redirect_from: - /github/administering-a-repository/about-dependabot + - /github/administering-a-repository/about-github-dependabot - /github/administering-a-repository/about-github-dependabot-version-updates versions: free-pro-team: '*' @@ -14,9 +15,9 @@ versions: {% data variables.product.prodname_dependabot %} は、依存関係を維持する手間を省きます。 これを使用して、リポジトリが依存するパッケージおよびアプリケーションの最新リリースに自動的に対応できるようにすることができます。 -{% data variables.product.prodname_dependabot_version_updates %} を有効にするには、リポジトリに設定ファイルをチェックインします。 設定ファイルでは、リポジトリに保存されているマニフェストまたは他のパッケージ定義ファイルの場所を指定します。 {% data variables.product.prodname_dependabot %} はこの情報を使用して、古いパッケージとアプリケーションをチェックします。 {% data variables.product.prodname_dependabot %} は、依存関係のセマンティックバージョニング（[semver](https://semver.org/)）を調べて、そのバージョンへの更新の必要性を判断することにより、依存関係の新しいバージョンの有無を決定します。 特定のパッケージマネージャーでは、{% data variables.product.prodname_dependabot_version_updates %} もベンダをサポートしています。 ベンダ (またはキャッシュ) された依存関係は、マニフェストで参照されるのではなく、リポジトリ内の特定のディレクトリにチェックインされる依存関係です。 パッケージサーバーが利用できない場合でも、ビルド時にベンダ依存関係を利用できます。 {% data variables.product.prodname_dependabot_version_updates %} は、ベンダの依存関係をチェックして新しいバージョンを確認し、必要に応じて更新するように設定できます。 +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} はこの情報を使用して、古いパッケージとアプリケーションをチェックします。 {% data variables.product.prodname_dependabot %} は、依存関係のセマンティックバージョニング（[semver](https://semver.org/)）を調べて、そのバージョンへの更新の必要性を判断することにより、依存関係の新しいバージョンの有無を決定します。 特定のパッケージマネージャーでは、{% data variables.product.prodname_dependabot_version_updates %} もベンダをサポートしています。 Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. パッケージサーバーが利用できない場合でも、ビルド時にベンダ依存関係を利用できます。 {% data variables.product.prodname_dependabot_version_updates %} は、ベンダの依存関係をチェックして新しいバージョンを確認し、必要に応じて更新するように設定できます。 -{% data variables.product.prodname_dependabot %} が古い依存関係を特定すると、プルリクエストを発行して、マニフェストを依存関係の最新バージョンに更新します。 ベンダの依存関係の場合、{% data variables.product.prodname_dependabot %} はプルリクエストを生成して、古い依存関係を新しいバージョンに直接置き換えます。 テストに合格したことを確認し、プルリクエストの概要に含まれている変更履歴とリリースノートを確認して、マージします。 詳しい情報については、「[バージョン更新の有効化と無効化](/github/administering-a-repository/enabling-and-disabling-version-updates)」を参照してください。 +{% data variables.product.prodname_dependabot %} が古い依存関係を特定すると、プルリクエストを発行して、マニフェストを依存関係の最新バージョンに更新します。 For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. テストに合格したことを確認し、プルリクエストの概要に含まれている変更履歴とリリースノートを確認して、マージします。 詳しい情報については、「[バージョン更新の有効化と無効化](/github/administering-a-repository/enabling-and-disabling-version-updates)」を参照してください。 セキュリティアップデートを有効にすると、{% data variables.product.prodname_dependabot %} はプルリクエストを発行し、脆弱性のある依存関係を更新します。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照してください。 diff --git a/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md b/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md index d864e219ca..afb3dd7a2e 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-protected-branches.md @@ -82,13 +82,13 @@ After enabling required status checks, all required status checks must pass befo {% endnote %} -必須ステータスチェックのタイプは、\[loose\] (寛容)、\[strict\] (厳格) のいずれかに設定できます。 The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging. +必須ステータスチェックのタイプは、\[loose\] (寛容)、\[strict\] (厳格) のいずれかに設定できます。 選択した必須ステータスチェックのタイプにより、マージする前にブランチをベースブランチとともに最新にする必要があるかどうかが決まります。 -| 必須ステータスチェックのタイプ | 設定 | マージの要件 | 留意点 | -| --------------- | --------------------------------------------------------------------------- | ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | -| **Strict** | [**Require branches to be up-to-date before merging**] チェックボックスにチェックする | マージ前、ブランチは、base ブランチとの関係で**最新でなければならない**。 | これは、必須ステータスチェックのデフォルト動作です。 他のコラボレーターが、保護された base ブランチにプルリクエストをマージした後に、あなたは head ブランチをアップデートする必要が出てくる可能性があるため、追加のビルドが必要になるかもしれません。 | -| **Loose** | [**Require branches to be up-to-date before merging**] チェックボックスにチェック**しない** | マージ前、ブランチは base ブランチとの関係で**最新でなくてもよい**。 | 他のコラボレーターがプルリクエストをマージした後に head ブランチをアップデートする必要はないことから、必要となるビルドは少なくなります。 base ブランチと競合する変更がある場合、ブランチをマージした後のステータスチェックは失敗する可能性があります。 | -| **無効** | [**Require status checks to pass before merging**] チェックボックスにチェック**しない** | ブランチのマージについての制限はない | 必須ステータスチェックが有効化されていない場合、base ブランチにあわせてアップデートされているかどうかに関わらず、コラボレーターはいつでもブランチをマージできます。 このことで、変更の競合が発生する可能性が高まります。 | +| 必須ステータスチェックのタイプ | 設定 | マージの要件 | 留意点 | +| --------------- | ------------------------------------------------------------------------------------- | ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | +| **Strict** | The **Require branches to be up to date before merging** checkbox is checked. | マージ前、ブランチは、base ブランチとの関係で**最新でなければならない**。 | これは、必須ステータスチェックのデフォルト動作です。 他のコラボレーターが、保護された base ブランチにプルリクエストをマージした後に、あなたは head ブランチをアップデートする必要が出てくる可能性があるため、追加のビルドが必要になるかもしれません。 | +| **Loose** | The **Require branches to be up to date before merging** checkbox is **not** checked. | マージ前、ブランチは base ブランチとの関係で**最新でなくてもよい**。 | 他のコラボレーターがプルリクエストをマージした後に head ブランチをアップデートする必要はないことから、必要となるビルドは少なくなります。 base ブランチと競合する変更がある場合、ブランチをマージした後のステータスチェックは失敗する可能性があります。 | +| **無効** | [**Require status checks to pass before merging**] チェックボックスにチェック**しない** | ブランチのマージについての制限はない | 必須ステータスチェックが有効化されていない場合、base ブランチにあわせてアップデートされているかどうかに関わらず、コラボレーターはいつでもブランチをマージできます。 このことで、変更の競合が発生する可能性が高まります。 | For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." diff --git a/translations/ja-JP/content/github/administering-a-repository/about-securing-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/about-securing-your-repository.md index 17fee43a33..0988980c85 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-securing-your-repository.md @@ -14,6 +14,8 @@ versions: {% data variables.product.prodname_dotcom %} には、コードを安全に保つために役立つセキュリティ機能が追加されています。 これらは、リポジトリの [**セキュリティ**] タブにあります。 +#### Available for all repositories + {% if currentVersion == "free-pro-team@latest" %} - **セキュリティポリシー** @@ -43,15 +45,23 @@ Use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %} + +These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} + - **{% data variables.product.prodname_code_scanning_capc %} アラート** 新しいコードまたは変更されたコードのセキュリティの脆弱性とコーディングエラーを自動的に検出します。 潜在的な問題が強調表示され、あわせて詳細情報も確認できるため、デフォルトのブランチにマージする前にコードを修正できます。 詳しい情報については、「[コードスキャニングについて](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)」を参照してください。 - **検出されたシークレット** -View any secrets that - {% data variables.product.prodname_dotcom %} has found in your code. リポジトリにチェックインされたトークンまたは資格情報は、侵害されたものとして扱う必要があります。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 - {% endif %} + {% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else if %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. リポジトリにチェックインされたトークンまたは資格情報は、侵害されたものとして扱う必要があります。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +- **依存関係のレビュー** - プルリクエストをマージする前に、依存関係に対する変更の影響を詳細に示し、脆弱性なバージョンがあればその詳細を確認できます。 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 %} ### 依存関係を調べる {% data variables.product.prodname_dotcom %} の依存関係グラフを使用すると、次の情報を調べることができます。 @@ -59,6 +69,6 @@ View any secrets that * リポジトリが依存しているエコシステムとパッケージ * リポジトリに依存しているリポジトリとパッケージ -You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. +You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. {% if currentVersion == "free-pro-team@latest" %}Enabling the dependency graph also enables {% data variables.product.prodname_dotcom %} to run dependency reviews of pull requests.{% endif %} 依存関係グラフは、リポジトリの [**Insights**] タブにあります。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 diff --git a/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md index 28a54a01e3..8e858e95e2 100644 --- a/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md +++ b/translations/ja-JP/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -27,13 +27,13 @@ versions: {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) 5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) 6. When you enable {% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. - ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png) + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} 4. To the right of " {% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index e19203c066..5ff425d08d 100644 --- a/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -4,13 +4,12 @@ intro: "You can allow or disallow auto-merge for pull requests in your repositor product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' permissions: People with maintainer permissions can manage auto-merge for pull requests in a repository. --- -{% data reusables.pull_requests.auto-merge-release-phase %} - If you allow auto-merge for pull requests in your repository, people can configure individual pull requests in the repository to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Under "Merge button", select or deselect **Allow auto-merge**. ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) \ No newline at end of file +1. Under "Merge button", select or deselect **Allow auto-merge**. ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) diff --git a/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index ca6118fe29..ea116e9217 100644 --- a/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -33,10 +33,15 @@ You can manage the security and analysis features for your {% if currentVersion {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} 4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 -{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} +**Note:** If you disable + + {% data variables.product.prodname_GH_advanced_security %}, both {% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail. + {% endnote %} + + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} ![[Configure security and analysis] 機能の [Enable] または [Disable] ボタン](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) {% endif %} diff --git a/translations/ja-JP/content/github/administering-a-repository/securing-your-repository.md b/translations/ja-JP/content/github/administering-a-repository/securing-your-repository.md index bd8aff7c2d..a5f2110023 100644 --- a/translations/ja-JP/content/github/administering-a-repository/securing-your-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/securing-your-repository.md @@ -6,5 +6,6 @@ redirect_from: - /articles/securing-your-repository versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- diff --git a/translations/ja-JP/content/github/administering-a-repository/setting-repository-visibility.md b/translations/ja-JP/content/github/administering-a-repository/setting-repository-visibility.md index 04d2c9c04d..254ae23e77 100644 --- a/translations/ja-JP/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/ja-JP/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,7 +24,7 @@ Organization のオーナーは、リポジトリの可視性を変更する機 * If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} * If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %} * Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} * {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/ja-JP/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md index 0b2e636839..6885f3d15d 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md +++ b/translations/ja-JP/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md @@ -33,14 +33,18 @@ versions: Comment: GitHub key Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? ``` -7. `O` を入力して選択した内容を保存してください。 +7. Enter `O` to confirm your selections. 8. キーのパスフレーズを入力してください。 -9. `gpg --armor --export GPG key ID` と入力してください。GPG key ID は使いたいキーの ID で置き換えてください。 以下の例では、GPG キー ID は `3AA5C34371567BD2` です。 +9. Enter `gpg> save` to save the changes + ```shell + $ gpg> save + ``` +10. `gpg --armor --export GPG key ID` と入力してください。GPG key ID は使いたいキーの ID で置き換えてください。 以下の例では、GPG キー ID は `3AA5C34371567BD2` です。 ```shell $ gpg --armor --export 3AA5C34371567BD2 # ASCII armor 形式で GPG キーを出力する ``` -10. [GPG キーを GitHub アカウントに追加](/articles/adding-a-new-gpg-key-to-your-github-account)することで、GPG キーをアップロードしてください。 +11. [GPG キーを GitHub アカウントに追加](/articles/adding-a-new-gpg-key-to-your-github-account)することで、GPG キーをアップロードしてください。 ### 参考リンク diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index 17415f8bb7..2cf518acba 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -4,10 +4,9 @@ intro: 'プルリクエストの自動マージを有効にすると、すべて product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' --- -{% data reusables.pull_requests.auto-merge-release-phase %} - ### 自動マージについて プルリクエストの自動マージを有効にすると、必要なすべてのレビューを満たし、ステータスチェックに合格すると、プルリクエストが自動的にマージされます。 自動マージにより、要件が満たされるのを待つ必要がなくなるため、他のタスクに進むことができます。 diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index b09eb899a9..667994cb11 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -9,7 +9,6 @@ versions: github-ae: '*' --- - ### プルリクエストのマージについて プルリクエストでは、head ブランチに加えた変更をベースブランチにマージすることを提案します。 デフォルトでは、head ブランチがベースブランチとコンフリクトしていない限り、どのプルリクエストもいつでもマージできます。 However, there may be restrictions on when you can merge a pull request into a specific branch. たとえば、必須のステータスチェックに合格した場合にのみ、プルリクエストをデフォルトブランチにマージできます。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)を参照してください。 diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index d115ece6a1..f99429e8a9 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -23,7 +23,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Team がコードレビューの割り当てを有効にしている場合、個々の承認は、保護されたブランチでのコードオーナーの承認要件を満たしません。 詳しい情報については、「[Team のコードレビューの割り当てを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)」を参照してください。{% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ファイルにコードオーナーがいる場合、プルリクエストをオープンする前にコードオーナーを確認できます。 リポジトリでは、ファイルを参照して {% octicon "shield-lock" aria-label="The edit icon" %}. diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index 4aa8d8ba48..9684696ef4 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -1,6 +1,6 @@ --- -title: コードスキャンニングについて -intro: '{% data variables.product.prodname_code_scanning %} を使用して、{% data variables.product.prodname_dotcom %} 上のプロジェクトのコードからセキュリティの脆弱性とエラーを見つけることができます。' +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/managing-security-vulnerabilities/about-automated-code-scanning @@ -12,39 +12,40 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### {% data variables.product.prodname_code_scanning %} について +### About {% data variables.product.prodname_code_scanning %} {% data reusables.code-scanning.about-code-scanning %} -{% data variables.product.prodname_code_scanning %} を使用して、コード内の既存の問題の修正を検索し、トリアージして、優先順位を付けることができます。 また、{% data variables.product.prodname_code_scanning_capc %} は、開発者による新しい問題の発生も防ぎます。 スキャンを特定の日時にスケジュールしたり、プッシュなどの特定のイベントがリポジトリで発生したときにスキャンをトリガーしたりすることができます。 +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. -{% data variables.product.prodname_code_scanning %} がコードに潜在的な脆弱性またはエラーを見つけた場合、{% data variables.product.prodname_dotcom %} はリポジトリにアラートを表示します。 アラートを引き起こしたコードを修正すると、{% data variables.product.prodname_dotcom %}はそのアラートを閉じます。 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)." +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 webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see +"[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." -{% data variables.product.prodname_code_scanning %} を始めるには、「[{% data variables.product.prodname_code_scanning %} の有効化](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)」を参照してください。 +To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." -### {% data variables.product.prodname_codeql %} について +### About {% data variables.product.prodname_codeql %} -デフォルトでは、{% data variables.product.prodname_code_scanning %} はセマンティックコード分析エンジンである {% data variables.product.prodname_codeql %} を使用します。 {% 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 %} は {% data variables.product.prodname_codeql %} を動作させるクエリ言語です。 {% data variables.product.prodname_ql %} はオブジェクト指向ロジックプログラミング言語です。 {% data variables.product.company_short %}、言語の専門家、セキュリティ研究者が {% data variables.product.prodname_code_scanning %} に使用するクエリを作成します。クエリはオープンソースです。 コミュニティはクエリを維持および更新して、分析を改善し、誤検出を減らします。 詳しい情報については、GitHub Security Lab Web サイトの「[{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql)」を参照してください。 +{% 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 %} の API エンドポイントについての詳細は、「[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)」を参照してください。 +{% 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 %} -[`github/codeql`](https://github.com/github/codeql)リポジトリで {% data variables.product.prodname_code_scanning %} のクエリを表示して貢献できます。 詳しい情報については、 {% data variables.product.prodname_codeql %} ドキュメントの「[{% data variables.product.prodname_codeql %} クエリ](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html)」を参照してください。 +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" %} -### {% data variables.product.prodname_code_scanning %}の支払いについて +### About billing for {% data variables.product.prodname_code_scanning %} -{% data variables.product.prodname_code_scanning_capc %} は {% data variables.product.prodname_actions %} を使用し、{% data variables.product.prodname_code_scanning %} ワークフローの実行ごとに {% data variables.product.prodname_actions %} に数分かかります。 詳しい情報については、[{% data variables.product.prodname_actions %}の支払いについて](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)を参照してください。 +{% 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 %} @@ -52,9 +53,9 @@ To monitor results from {% data variables.product.prodname_code_scanning %} acro {% data reusables.code-scanning.get-started-uploading-third-party-data %} -### 参考リンク +### Further reading {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} - [{% data variables.product.prodname_security %}](https://securitylab.github.com/) -- OASIS 委員会 の Web サイトの「[OASIS Static Analysis Results Interchange Format (SARIF) 」TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) +- [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/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 25ed0126b4..42a03bc5b3 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -134,19 +134,22 @@ Attempts to build the code for the compiled languages C/C++, C#, and Java. For t Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_location %}. -| Flag | 必須 | Input value | -| -------------------------------- |:--:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--repository` | ✓ | 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` | | なし. 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` | | なし. Prints more verbose output. | -| `-h`, `--help` | | なし. Displays help for the command. | +| Flag | 必須 | Input value | +| ---------------------------------- |:--:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `--repository` | ✓ | 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` | | なし. 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. | +| `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. | +| `--no-add-snippets` | | なし. Excludes code snippets from the SARIF output. | +| `--threads` | | Number of threads to use when running queries. The default is to use all available cores. | +| `--temp-dir` | | Directory where temporary files are stored. The default is _./codeql-runner_. | +| `--debug` | | なし. Prints more verbose output. | +| `-h`, `--help` | | なし. Displays help for the command. | #### `アップロード` diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md index b427d2bf6f..7bbe619f9c 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md @@ -17,7 +17,7 @@ versions: ### About the {% data variables.product.prodname_codeql_workflow %} and compiled languages -You enable {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. デフォルトの {% data variables.product.prodname_code_scanning %} ワークフローは、`on.push` イベントを使用して、ワークフローファイルを含むブランチへのプッシュごとにコードスキャンをトリガーします。 +You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} For general information about configuring diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md index eaf6f35ba9..12d36eba42 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md @@ -14,7 +14,7 @@ versions: {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %} {% link_in_list /about-code-scanning %} {% link_in_list /triaging-code-scanning-alerts-in-pull-requests %} - {% link_in_list /enabling-code-scanning %} + {% link_in_list /setting-up-code-scanning-for-a-repository %} {% link_in_list /managing-code-scanning-alerts-for-your-repository %} {% link_in_list /configuring-code-scanning %} {% link_in_list /configuring-the-codeql-workflow-for-compiled-languages %} diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index f8364118a5..a3f5f1773d 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -16,7 +16,7 @@ redirect_from: ### {% data variables.product.prodname_code_scanning %} からのアラートについて -You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. デフォルトの {% data variables.product.prodname_code_scanning %} ワークフローは、`on.push` イベントを使用して、ワークフローファイルを含むブランチへのプッシュごとにコードスキャンをトリガーします。 +You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." @@ -28,7 +28,7 @@ Each alert highlights a problem with the code and the name of the tool that iden ![{% data variables.product.prodname_code_scanning %} からのアラートの例](/assets/images/help/repository/code-scanning-alert.png) -If you enable {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information. +If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information. {% data variables.product.prodname_code_scanning %} がデータフローアラートを報告すると、{% data variables.product.prodname_dotcom %} はデータがコードを通してどのように移動するかを示します。 {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users. @@ -65,7 +65,7 @@ Closing an alert is a way to resolve an alert that you don't think needs to be f ### Dismissing or deleting alerts -There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have enabled a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have enabled {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab. +There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab. Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab. @@ -127,5 +127,5 @@ If a project has multiple alerts that you want to dismiss for the same reason, y ### 参考リンク - "[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)" -- "[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)" +- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" - "[About integration with {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)" diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index ca841f17d1..42d0f34660 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -24,7 +24,7 @@ If you use a continuous integration or continuous delivery/deployment (CI/CD) sy {% 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)." +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 "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-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. diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 4f4a58e944..cdcaf057b0 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -97,7 +97,6 @@ You can check a SARIF file is compatible with {% data variables.product.prodname | `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)」を参照してください。 | -| `suppressions[].state` | **任意。**`state` が `accepted` に設定されている場合、{% data variables.product.prodname_code_scanning %} は {% data variables.product.prodname_dotcom %} の状態を `Closed` に更新します。 | #### `location` オブジェクト diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md new file mode 100644 index 0000000000..8a62d225b7 --- /dev/null +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -0,0 +1,117 @@ +--- +title: Setting up code scanning for a repository +shortTitle: Setting up code scanning +intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.' +redirect_from: + - /github/managing-security-vulnerabilities/configuring-automated-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} + +### Options for setting up {% data variables.product.prodname_code_scanning %} + +You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to 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. 詳しい情報については、「[{% 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 %} + +### Setting up {% 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. 詳しい情報については、「[{% 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 %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/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) +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. + + 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)」を参照してください。 +6. [**Start commit**] ドロップダウンを使用して、コミットメッセージを入力します。 ![コミットを開始する](/assets/images/help/repository/start-commit-commit-new-file.png) +7. デフォルトブランチに直接コミットするか、新しいブランチを作成してプルリクエストを開始するかを選択します。 ![コミット先を選択する](/assets/images/help/repository/start-commit-choose-where-to-commit.png) +8. [**Commit new file**] または [**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. As a result, {% data variables.product.prodname_code_scanning %} will now commence. + +### 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. 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. + +### 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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. + + ![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 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. + +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, 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 %}. + +### 次のステップ + +After setting up {% 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 set up {% 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. 詳しい情報については、「[通知を設定する](/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. 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} を設定する](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)」を参照してください。 diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index 572a1b0ed1..7cdeaca040 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -15,7 +15,7 @@ versions: 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, 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 notices and the check succeeds. If your pull request targets a protected branch that has been enabled for {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。 +If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, 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 notices and the check succeeds. 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 you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。 ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md index 4962fa7285..22ed12a256 100644 --- a/translations/ja-JP/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -24,7 +24,7 @@ versions: - High - Critical -{% data variables.product.prodname_advisory_database %} は、CVSS バージョン 3.0 標準と上記の CVSS レベルを使用します。 {% data variables.product.product_name %} は CVSS スコアを公開しません。 +{% data variables.product.prodname_advisory_database %} は、CVSS バージョン 3.0 標準と上記の CVSS レベルを使用します。 {% data reusables.repositories.github-security-lab %} @@ -41,24 +41,39 @@ versions: {% endnote %} ### {% data variables.product.prodname_advisory_database %} を検索する -データベースを検索し、修飾子を使用して、特定の日付、特定のエコシステム、または特定のライブラリで作成されたアドバイザリに検索を絞り込むことができます。 + +You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| 修飾子 | サンプル | -| --------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) は、NPM パッケージに影響するアドバイザリのみを表示します。 | -| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) は、重大度レベルが高いアドバイザリのみを表示します。 | -| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) は、lodash ライブラリに影響するアドバイザリのみを表示します。 | -| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) は、一番古いアドバイザリを最初にソートします。 | -| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) は、一番新しいアドバイザリを最初にソートします。 | -| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) は、最近で最も更新されていないものを最初にソートします。 | -| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) は、最も直近で更新されたものを最初にソートします。 | -| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) は、撤回されたアドバイザリのみを表示します。 | -| `created:YYYY-MM-DD` | [**created:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2019-10-31) は、この日に作成されたアドバイザリのみを表示します。 | -| `updated:YYYY-MM-DD` | [**updated:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2019-10-31) は、この日に更新されたアドバイザリのみを表示します。 | +| 修飾子 | サンプル | +| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `GHSA-ID` | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | +| `CVE-ID` | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | +| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) は、NPM パッケージに影響するアドバイザリのみを表示します。 | +| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) は、重大度レベルが高いアドバイザリのみを表示します。 | +| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) は、lodash ライブラリに影響するアドバイザリのみを表示します。 | +| `cwe:ID` | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | +| `credit:USERNAME` | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | +| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) は、一番古いアドバイザリを最初にソートします。 | +| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) は、一番新しいアドバイザリを最初にソートします。 | +| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) は、最近で最も更新されていないものを最初にソートします。 | +| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) は、最も直近で更新されたものを最初にソートします。 | +| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) は、撤回されたアドバイザリのみを表示します。 | +| `created:YYYY-MM-DD` | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) は、この日に作成されたアドバイザリのみを表示します。 | +| `updated:YYYY-MM-DD` | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) は、この日に更新されたアドバイザリのみを表示します。 | + +### Viewing your vulnerable repositories + +For any vulnerability in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories have a {% data variables.product.prodname_dependabot %} alert for that vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)」を参照してください。 + +1. Https://github.com/advisories にアクセスします。 +2. Click an advisory. +3. At the top of the advisory page, click **Dependabot alerts**. ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png) +4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) +5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name. ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index 120212ad6c..f2580f67ea 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -12,6 +12,8 @@ versions: {% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." +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 %} usage beyond the amounts including with your account. 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)." + 利用時間 (分) は毎月リセットされますが、ストレージはリセットされません。 | 製品 | ストレージ | 分 (月あたり) | diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 9d2feebf2d..1beb255256 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.package_registry.container-registry-beta-billing-note %} +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_registry %} usage beyond the amounts including with your account. 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)." + データ転送は毎月リセットされますが、ストレージはリセットされません。 | 製品 | ストレージ | データ転送 (月あたり) | diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 56c92bc629..9ad0baa99a 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} 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)." +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 %} usage beyond the amounts including with your account. 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)." + As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. たとえば、Organizationで {% data variables.product.prodname_team %} を使用していて超過を許可しておらず、月あたりのストレージ使用量が1.9GBから2.1GBに増えるワークフローアーティファクトを作成した場合、ストレージは製品に含まれる2GBをわずかに超えることになります。 Because you have not enabled overages, your next attempt to create a workflow artifact will fail. その月の0.1GBの超過分について請求書は発行されません。 However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue. @@ -42,7 +44,7 @@ Organization の {% data variables.product.prodname_actions %} については ### Enterprise アカウントの {% data variables.product.prodname_actions %} に対する利用上限を管理する -Enterprise アカウントの {% data variables.product.prodname_actions %} については、Enterprise オーナーと支払いマネージャーが利用上限を管理できます。 +Enterprise アカウントの {% data variables.product.prodname_actions %} の利用上限は、Enterprise オーナーと支払いマネージャーが管理できます。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index 7de51df986..35f3b7dcd2 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} 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)." +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_registry %} usage beyond the amounts including with your account. 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)." + As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. たとえば、Organizationで {% data variables.product.prodname_team %} を使用していて超過を許可しておらず、月あたりのストレージ使用量が1.9GBから2.1GBに増えるプライベートパッケージの新しいバージョンを発行した場合、ストレージは製品に含まれる2GBをわずかに超えることになります。 超過を有効にしていなかったため、次にパッケージのバージョンを発行しようとしても失敗します。 その月の0.1GBの超過分について請求書は発行されません。 However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue. diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index d9c45b5812..8729157875 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -23,8 +23,13 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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. +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. +{% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@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.{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) {% endif %} @@ -42,24 +47,21 @@ You can enable or disable features for all repositories. {% if currentVersion == 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)." 1. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。 - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) {% endif %} 2. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。 - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) {% endif %} -1. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。 - {% if currentVersion == "free-pro-team@latest" %} +3. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) {% endif %} @@ -68,10 +70,9 @@ You can enable or disable features for all repositories. {% if currentVersion == 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)." 1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories {% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) {% endif %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 9a96b90e09..afbf2c1e5a 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -70,7 +70,7 @@ Organization レベルの設定を管理することに加え、Organization の {% endif %} | Apply/dismiss labels | | **X** | **X** | **X** | **X** | | Create, edit, delete labels | | | **X** | **X** | **X** | -| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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 %} | マイルストーンの適用 | | **X** | **X** | **X** | **X** | @@ -150,8 +150,8 @@ In this section, you can find the repository permission levels required for secu | リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | | [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | | 脆弱な依存関係についての[{% data variables.product.prodname_dependabot_alerts %}を受信する個人または Team の追加指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** | -| [セキュリティアドバイザリ](/github/managing-security-vulnerabilities/about-github-security-advisories)の作成 | | | | | **X** | -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| [セキュリティアドバイザリ](/github/managing-security-vulnerabilities/about-github-security-advisories)の作成 | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | プライベートリポジトリの[依存関係グラフの有効化](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) | | | | | **X** | | [View dependency reviews](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | [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** | diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md new file mode 100644 index 0000000000..ea9b3d4b19 --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md @@ -0,0 +1,40 @@ +--- +title: Connecting an Azure subscription to your enterprise +intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the included amounts for your enterprise.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise +versions: + free-pro-team: '*' +--- + +### About Azure subscriptions and {% data variables.product.product_name %} + +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 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) and "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." + +After you connect an Azure subscription, you can also manage your spending limit. For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)" and "[Managing your spending limit for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)." + +### Connecting your Azure subscription to your enterprise account + +To connect your Azure subscription, you must have owner permissions to the subscription. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Payment Information", click **Add Azure Subscription**. +1. To sign in to your Microsoft account, follow the prompts. +1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**. +1. Under "Select a subscription", select the Azure Subscription ID that you want to connect to your enterprise. +1. Click **Connect**. + +### Disconnecting your Azure subscription from your enterprise account + +After you disconnect your Azure subscription from your enterprise account, your usage can no longer exceed the amounts included with your plan. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. +1. Review the prompt, then click **Remove**. 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 84528000d4..7983203a77 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 @@ -18,6 +18,7 @@ versions: {% link_in_list /about-enterprise-accounts %} {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %} {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %} + {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %} {% topic_link_in_list /managing-users-in-your-enterprise %} {% link_in_list /roles-in-an-enterprise %} {% link_in_list /inviting-people-to-manage-your-enterprise %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md index af230c0b0e..c1c6a9a9c7 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md @@ -31,7 +31,7 @@ Enterprise owners have complete control over the enterprise and can take every a Enterprise オーナーは、Organization のオーナーになるか、Organization が所有するリポジトリに直接アクセスする権限を与えられない限り、Organization の設定またはコンテンツにはアクセスできません。 Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. -You can add as many enterprise owners as you'd like to your enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. +An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. ### Enterprise メンバー @@ -52,7 +52,7 @@ Billing managers only have access to your enterprise's billing settings. Billing - 支払いマネージャーのリストを閲覧 - 他の支払いマネージャーの追加または削除 -Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. 支払いマネージャーは、{% data variables.product.prodname_dotcom %} 上に個人アカウントを持っていなければなりません。 +Billing managers will only consume a license if they are an owner or member of at least one organization within the enterprise. Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. 支払いマネージャーは、{% data variables.product.prodname_dotcom %} 上に個人アカウントを持っていなければなりません。 ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index a0c077b2f7..c0f78deb4c 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -15,6 +15,8 @@ versions: 現時点では、Enterprise アカウントは請求書で支払いを行っている {% data variables.product.prodname_enterprise %} のお客様が利用できます。 Enterprise アカウントに接続されたすべての Organization および {% data variables.product.prodname_ghe_server %} インスタンスの支払いは、すべての有料の {% data variables.product.prodname_dotcom_the_website %} サービス (これには Organization の有料ライセンス、{% data variables.large_files.product_name_long %} のデータパック、{% data variables.product.prodname_marketplace %} アプリケーションに対するプランが含まれます) に対する単一の支払いに集約されます。 +{% if currentVersion == "free-pro-team@latest" %}{% 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)."{% endif %} + For more information about managing billing managers, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." ### Enterprise アカウントのプランおよび利用状況を表示する diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index 51a455487a..1afddbd128 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -50,7 +50,7 @@ You can also {% if currentVersion == "free-pro-team@latest" %}invite{% else %}ad | リポジトリのコードオーナーを定義する | 「[コードオーナー'について](/github/creating-cloning-and-archiving-repositories/about-code-owners)」 | | Archive the repository | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | -| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" | +| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} | Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %} ### Collaborator access for a repository owned by a user account diff --git a/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index 9bdefe9767..9af7878f29 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -25,8 +25,6 @@ Jekyll を使用して {% data variables.product.prodname_pages %} サイトを {% 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 %} @@ -36,6 +34,8 @@ Jekyll を使用して {% data variables.product.prodname_pages %} サイトを {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% data reusables.command_line.open_the_multi_os_terminal %} 2. リポジトリのローカルコピーがまだない場合、サイトのソースファイルを保存したい場所に移動します。_PARENT-FOLDER_ は、リポジトリを保存したいフォルダの名前に置き換えてください。 ```shell diff --git a/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site.md b/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site.md index 54dcf8fa15..54227153d8 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site.md +++ b/translations/ja-JP/content/github/working-with-github-pages/creating-a-github-pages-site.md @@ -20,8 +20,6 @@ versions: {% 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 %} @@ -33,6 +31,8 @@ versions: {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% data reusables.pages.navigate-site-repo %} {% data reusables.pages.decide-publishing-source %} 3. 選択した公開元が既に存在する場合、公開元に移動します。 選択した公開元がまだ存在しない場合は、公開元を作成します。 diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md index 7d1cceffdf..63ef9134f5 100644 --- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md +++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports.md @@ -1,16 +1,18 @@ --- -title: 利用可能なメトリクスとレポートの管理 -intro: '{% data variables.product.prodname_insights %}にわたって特定のメトリクスを有効化あるいは無効化できます。' +title: Managing available metrics and reports +intro: 'You can enable and disable specific metrics across {% data variables.product.prodname_insights %}.' product: '{% data reusables.gated-features.github-insights %}' redirect_from: - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights -permissions: '{% data variables.product.prodname_insights %}の管理権限を持っている人は、利用可能なメトリクスやレポートを管理できます。' +permissions: 'People with admin permissions to {% data variables.product.prodname_insights %} can manage available metrics and reports.' versions: enterprise-server: '*' --- -メトリクスを無効化すると、そのメトリクスはどのユーザからも、{% data variables.product.prodname_insights %}のどこからも見えなくなります。 +When you disable a metric, the metric will not be visible for any user, anywhere on {% data variables.product.prodname_insights %}. {% data reusables.github-insights.settings-tab %} -2. **{% octicon "gear" aria-label="The gear icon" %} Settings（設定）**の下で、**Toggle reports（レポートの切り替え）**をクリックしてください。 ![レポートの切り替えタブ](/assets/images/help/insights/toggle-reports-tab.png) -3. 管理したいメトリクスの右で、** Enabled（有効）**あるいは**Disabled（無効）**ドロップダウンメニューを使ってください。 ![メトリクスの切り替えのドロップダウンメニュー](/assets/images/help/insights/toggle-report-drop-down.png) +2. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Toggle reports**. + ![Toggle reports tab](/assets/images/help/insights/toggle-reports-tab.png) +3. To the right of the metric you want to manage, use the **Enabled** or **Disabled** drop-down menu. + ![Drop-down menu to toggle metric](/assets/images/help/insights/toggle-report-drop-down.png) diff --git a/translations/ja-JP/content/rest/overview/libraries.md b/translations/ja-JP/content/rest/overview/libraries.md index 8406007a6b..5fd19e461a 100644 --- a/translations/ja-JP/content/rest/overview/libraries.md +++ b/translations/ja-JP/content/rest/overview/libraries.md @@ -25,7 +25,7 @@ versions: ### Clojure -ライブラリ名 | リポジトリ |---|---| **Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles) +Library name | Repository |---|---| **Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles) ### Dart @@ -57,7 +57,7 @@ versions: ### Julia -ライブラリ名 | リポジトリ | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl) +Library name | Repository | |---|---| **GitHub.jl**|[WestleyArgentum/GitHub.jl](https://github.com/WestleyArgentum/GitHub.jl) ### OCaml @@ -65,11 +65,11 @@ versions: ### Perl -ライブラリ名 | リポジトリ | ライブラリの metacpan ウェブサイト |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub) +Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub) ### PHP -ライブラリ名 | リポジトリ |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI) +ライブラリ名 | リポジトリ |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GitHubAPI](https://github.com/FlexyProject/GitHubAPI) ### Python diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md index ef8ff48e1f..09ce10dc7d 100644 --- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md @@ -129,7 +129,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar > { > "message": "Bad credentials", -> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -141,7 +141,7 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f > 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" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -357,7 +357,7 @@ new Date(1372700873 * 1000) > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#rate-limiting" > } ``` @@ -402,7 +402,7 @@ Basic 認証または OAuth を使用してレート制限を超えた場合、A > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#abuse-rate-limits" > } ``` diff --git a/translations/ja-JP/content/rest/reference/repos.md b/translations/ja-JP/content/rest/reference/repos.md index d2588f8ba5..1a2759c9ec 100644 --- a/translations/ja-JP/content/rest/reference/repos.md +++ b/translations/ja-JP/content/rest/reference/repos.md @@ -141,7 +141,7 @@ GitHub は、あなたのサーバーに実際にアクセスすることはな ### 非アクティブのデプロイメント -デプロイメントのステータスを `success` に設定すると、同じリポジトリ内の一時的でない、非本番環境のデプロイメントはすべて `inactive` になります。 これを回避するには、デプロイメントのステータスを作成する前に、`auto_inactive` を `false` に設定します。 +When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository to the same environment name will become `inactive`. これを回避するには、デプロイメントのステータスを作成する前に、`auto_inactive` を `false` に設定します。 `state` を `inactive` に設定することで、一時的な環境が存在しなくなったことを伝えることができます。 `state` を `inactive` に設定すると、{% data variables.product.prodname_dotcom %} でデプロイメントが `destroyed` と表示され、アクセス権が削除されます。 diff --git a/translations/ja-JP/data/glossaries/external.yml b/translations/ja-JP/data/glossaries/external.yml index 942ae8ded6..664c70ee67 100644 --- a/translations/ja-JP/data/glossaries/external.yml +++ b/translations/ja-JP/data/glossaries/external.yml @@ -24,7 +24,7 @@ - term: 認証コード description: >- - A code you'll supply, in addition to your GitHub password, when signing in with 2FA via the browser. This code is either generated by an application or delivered to your phone via text message. Also called a "2FA authentication code." + ブラウザから2FA でサインインする際、GitHub パスワードに加えて入力するコード。このコードは、アプリケーションで生成されるか、テキストメッセージによってスマートフォンに送信されます。「2FA 認証コード」ともいいます。 - term: ベースブランチ description: プルリクエストをマージする際に変更が組み込まれるブランチ。プルリクエストを作成する際には、必要であればベースブランチをリポジトリのデフォルトブランチから他のブランチに変更できます。 diff --git a/translations/ja-JP/data/release-notes/2-21/0.yml b/translations/ja-JP/data/release-notes/2-21/0.yml index 469347560b..1f18ea1759 100644 --- a/translations/ja-JP/data/release-notes/2-21/0.yml +++ b/translations/ja-JP/data/release-notes/2-21/0.yml @@ -46,27 +46,27 @@ sections: - '管理者は、`ghe-webhook-manage`を使ってコマンドラインからwebhook IDを利用してwebhookの有効化、無効化、削除、検索を行えます。{% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' - 'マージされたPull Requestに対する手動のhead参照のクリーンアップが行われた後、自動のベース再ターゲティングが行われます。{% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' - 'SVGファイルはdiffビュー内でテキスト及び画像として扱われます。{% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' - - 'The "auto delete branches on merge" setting can be set when creating and updating repositories using the REST API. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' - - 'A new endpoint has been added to delete a deployment through the REST API. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' - - 'Admins can [enable security alerts](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) but disable all notifications from those alerts. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' - - 'The Pages log shows the user login accessing the GitHub Pages site. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' - - 'Enterprise members can see all of the organizations they belong to as part of their Enterprise account from one view by navigating to `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' - - '[REST API support for triage and maintain roles](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) has been expanded. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' - - 'A user can create and share search queries that resolve to the current user by using the `@me` search syntax. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' - - 'New issue template configuration options have been [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' - - 'MySQL backup and restore reliability and time to completion has been improved. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' - - '[Improved visibility](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) of pull requests and issue references in the issue sidebar, issue cards and issue list. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' - - 'Users can filter and search by `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' - - 'Automatic failover of MySQL within a single region for Cluster deployments is now possible. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' - - 'A user can compare tags between two releases to determine what changes have been made on the releases page. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' - - 'Outdated comments are no longer collapsed by default on the Pull Request timeline. They can be collapsed by resolving the thread. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' - - 'Admins can view a list of logins reserved for internal use by navigating to the "Reserved logins" stafftools tab. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' + - 'REST APIを使用してリポジトリの作成や更新を行う際に、"auto delete branches on merge"を設定できます。{% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' + - 'REST APIを通じてデプロイメントを削除する、新しいエンドポイントが追加されました。{% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' + - '管理者は[セキュリティアラートを有効に](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)しながら、それらのアラートからのすべての通知を無効化できます。{% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' + - 'Pagesのログは、GitHub Pagesのサイトにアクセスしたユーザログインを示します。 {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' + - 'Enterpriseのメンバーは、`https://[ghes-hostname]/enterprises/[account-name]`にアクセスすることによって所属するすべてのOrganizationをEnterpriseアカウントの一部として1つのビューで見ることができます。{% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' + - '[トリアージと保守のロールのためのREST APIサポート](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/)が拡張されました。{% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' + - 'ユーザは、`@me`検索構文を使って、現在のユーザに解決される検索クエリを作成して共有できます。{% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' + - '新しいIssueのテンプレート設定オプションが[added]されました(https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/)。{% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' + - 'MySQLのバックアップ及びリストアの完了の信頼性と時間が改善されました。{% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' + - 'Issueサイドバー、Issueカード、Issueリスト内のPull RequestとIssueの参照の[可視性が改善](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/)されました。{% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - '`linked:pr`あるいは`linked:issue`でユーザがフィルタリングや検索ができるようになりました。{% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' + - 'クラスタデプロイメントにおいて、単一リージョン内でMySQLの自動フェイルオーバーが可能になりました。{% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' + - 'リリースページで、ユーザが2つのリリース間のタグを比較して、どういった変更が行われたかを判断できるようになりました。{% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' + - 'Pull Requestのタイムラインにおいて、古くなったコメントがデフォルトで折りたたまれなくなりました。スレッドを解決すれば、それらを折りたたむことができます。{% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' + - '管理者は、"Reserved logins"スタッフツールタブにアクセスすることによって、内部利用のために予約されたログインのリストを見ることができます。{% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - 'Gistへのプッシュの際に、post-receiveフックの間に例外がトリガーされることがあります。{% comment %} https://github.com/github/github/issues/129091 {% 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 %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。（2020-06-23更新）{% 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 %}' + - '監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。（2020-11-02更新）{% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/1.yml b/translations/ja-JP/data/release-notes/2-21/1.yml index 6177efb3a8..8c21670cae 100644 --- a/translations/ja-JP/data/release-notes/2-21/1.yml +++ b/translations/ja-JP/data/release-notes/2-21/1.yml @@ -2,19 +2,19 @@ date: '2020-06-23' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' bugs: - - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - 'The internal communication service used to access MySQL could restart more often than required, including part way through the upgrade process, which could cause the upgrade to partially fail. We have reduced the rate of restarts and made the code more robust. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' - - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" - - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' - - 'The "Repository issue deletion" Enterprise account policy did not reflect the currently saved setting. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' - - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' + - '転送のメカニズムとしてUDPが使用されている場合に、過度に大きなログイベントによってログのフォワーディングが不安定になることがありました。{% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - 'MySQLにアクセスするために使われる内部的な通信サービスが、アップグレードのプロセスの一部を含め、必要以上の頻度で再起動することがあり、それによってアップグレードが部分的に失敗することがありました。来期道の頻度を引き下げ、コードをより頑健にしました。{% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' + - "SSO経由のユーザの自動サスペンション解除が、すでにユーザアカウントに関連づけられているキーがSSHキーの属性にある場合に完了しませんでした。{% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'インターナルリポジトリへのプルアクセス権を持つビジネスメンバーについて、REST APIからのリポジトリ権限のハッシュがアクセス権を持たないと示していました。{% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' + - '"Repository issue deletion" Enterpriseアカウントポリシーが、現在保存されている設定を反映しませんでした。{% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' + - '監査ログにブランチ保護の変更イベントが含まれていませんでした。{% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - - '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 %}' + - '監査ログは実際のソースIPアドレスの代わりに127.0.0.1に起因する可能性があります。(updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/10.yml b/translations/ja-JP/data/release-notes/2-21/10.yml index 92088b6ad9..5154236ddc 100644 --- a/translations/ja-JP/data/release-notes/2-21/10.yml +++ b/translations/ja-JP/data/release-notes/2-21/10.yml @@ -2,14 +2,14 @@ date: '2020-10-20' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' bugs: - - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' + - 'Enterpriseアカウントの"Confirm two-factor requirement policy"メッセージが正しくありませんでした。{% comment %} https://github.com/github/github/pull/158736 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - - '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 %}' + - '監査ログは実際のソースIPアドレスの代わりに127.0.0.1に起因する可能性があります。(updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/11.yml b/translations/ja-JP/data/release-notes/2-21/11.yml index ed95c874c5..d5aee0920d 100644 --- a/translations/ja-JP/data/release-notes/2-21/11.yml +++ b/translations/ja-JP/data/release-notes/2-21/11.yml @@ -2,17 +2,17 @@ date: '2020-11-03' sections: security_fixes: - - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" - - 'Packages have been updated to the latest security versions. {% 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 %}' + - '**中:** SVNブリッジへの特別に細工されたリクエストによって引き起こされる高いCPU使用率によって、サービス拒否（DoS）が引き起こされる可能性がありました。{% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**低:** 不正確なトークンの検証によって、認証中のトークンのマッチのためのエントロピーが減少しました。分析からは、実際には大きなセキュリティ上のリスクはないことが示されています。{% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'パッケージが最新のセキュリティバージョンに更新されました。{% 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: - - 'Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' - - 'A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' + - '非ASCIIキャラクタを含むファイル名のIssueテンプレートを編集すると、"500 Internal Server Error"で失敗します。{% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' + - 'バックグラウンドジョブのメトリック収集方式のために、CPU使用率が増大しました。（2020-11-03更新）{% comment %} https://github.com/github/github/pull/160109 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' + - '監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。（--更新）{% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/12.yml b/translations/ja-JP/data/release-notes/2-21/12.yml index 8a11a3a985..2771ffc8b7 100644 --- a/translations/ja-JP/data/release-notes/2-21/12.yml +++ b/translations/ja-JP/data/release-notes/2-21/12.yml @@ -2,15 +2,15 @@ date: '2020-11-17' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' bugs: - - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' - - 'Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' + - 'baneldログに秒とマイクロ秒の間のセパレータが欠けていました。 {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'Enterpriseアカウントの"Repository visibility change"ポリシーが"Enabled"に設定されている場合、OrganizationオーナーがOrganization内のリポジトリの可視性を変更できませんでした。 {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' + - '監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。{% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' diff --git a/translations/ja-JP/data/release-notes/2-21/13.yml b/translations/ja-JP/data/release-notes/2-21/13.yml index ba364556bb..b97afab77f 100644 --- a/translations/ja-JP/data/release-notes/2-21/13.yml +++ b/translations/ja-JP/data/release-notes/2-21/13.yml @@ -2,18 +2,18 @@ date: '2020-12-03' sections: bugs: - - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' - - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% 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 %}' + - 'ブートストラップ時のレース条件により、認可サービスが不健全として検出され、再起動されることにつながりました。{% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' + - '下位の動作により、ホットパッチアップグレードのプロセス中に、サービスが利用できなくなりました{% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'ログ転送SSL証明書の一部が正しく適用されませんでした。{% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'サスペンドされたユーザがTeamあるいはOrganizationから削除されると、そのユーザにメール通知が送信されました。{% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'SSH証明書の適用方法が、OrganizationとBusiness間で整合していませんでした。{% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - '不正確なパスワードの利用のためにアカウントにレート制限が適用された場合に、最大で24時間ロックアウトされることがありました。{% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - '多くの参照を持つリポジトリ上のPull Requestの同期が、ワーカーキューを遅れさせることがありました。{% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' + - '特定のページへのアクセスを試みた後にサインインすると、意図したアクセス先ではなくホームページにユーザが送られてしまいました。{% 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: - - '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 %}' + - '新たにセットアップされたユーザを持たない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 %}' diff --git a/translations/ja-JP/data/release-notes/2-21/14.yml b/translations/ja-JP/data/release-notes/2-21/14.yml index 201c8ffdbb..bd29d06269 100644 --- a/translations/ja-JP/data/release-notes/2-21/14.yml +++ b/translations/ja-JP/data/release-notes/2-21/14.yml @@ -2,12 +2,12 @@ date: '2020-12-17' sections: security_fixes: - - '**LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' + - '**低:** SVNブリッジへの特別に細工されたリクエストによって引き起こされる高いCPU使用率によって、サービス拒否（DoS）が引き起こされる可能性がありました。{% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' diff --git a/translations/ja-JP/data/release-notes/2-21/2.yml b/translations/ja-JP/data/release-notes/2-21/2.yml index 6a19c2ef97..6ba5cb2daa 100644 --- a/translations/ja-JP/data/release-notes/2-21/2.yml +++ b/translations/ja-JP/data/release-notes/2-21/2.yml @@ -2,19 +2,19 @@ date: '2020-07-09' sections: security_fixes: - - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + - '**中:** nginxを1.16.1にアップデートし、CVE-2019-20372に対応しました。（2020-07-22更新）{% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' bugs: - - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' - - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - 'The VPN between nodes could become unstable causing errors to be logged and free space on the root volume to be exhausted. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' - - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' + - '特定のログファイルが7日ごとにローテートされませんでした。{% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'webhookのソースポートの頻繁な再利用によって、接続が拒否されました。{% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' + - '正しくないバックグラウンドジョブが、パッシブレプリカとして設定されたインスタンス上で動作しようとすることがありました。{% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'ノード間のVPNが不安定になり、そのためにエラーがログに記録され、ルートボリュームの空き領域が枯渇することがあります。{% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' + - 'SAMLが有効になっているOrganizationで、インターナルリポジトリが検索結果に正しく含まれていませんでした。{% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - - '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 %}' + - '監査ログは実際のソースIPアドレスの代わりに127.0.0.1に起因する可能性があります。(updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/3.yml b/translations/ja-JP/data/release-notes/2-21/3.yml index ceedf888c7..1413e25d1e 100644 --- a/translations/ja-JP/data/release-notes/2-21/3.yml +++ b/translations/ja-JP/data/release-notes/2-21/3.yml @@ -2,16 +2,16 @@ date: '2020-07-21' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% 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 %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% 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: - - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' - - "In some circumstances, accessing the 'Explore' page would throw an application error. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" + - '大きな画面において、管理コンソースのモニターグラフが適切に表示されないことがあります。{% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'SameSiteクッキーポリシーが適用されている場合に、GitHub Appマニフェストが作成したフローが利用できない状況がありました。{% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' + - "状況によっては、'Explore'ページにアクセスするとアプリケーションエラーが生じます。{% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - - '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 %}' + - '監査ログは実際のソースIPアドレスの代わりに127.0.0.1に起因する可能性があります。(updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/4.yml b/translations/ja-JP/data/release-notes/2-21/4.yml index 3b1c3b7b84..86d342c98d 100644 --- a/translations/ja-JP/data/release-notes/2-21/4.yml +++ b/translations/ja-JP/data/release-notes/2-21/4.yml @@ -2,26 +2,26 @@ date: '2020-08-11' sections: security_fixes: - - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**HIGH:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% 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 %}' + - '**重大:** 攻撃者がGitHub Pagesのサイトの構築の一部としてコマンドを実行できる、リモートコード実行の脆弱性がGitHub Pagesで特定されました。この問題は、Pagesのビルドプロセスで使われている古くて脆弱性のある依存関係によるものです。この脆弱性を突くには、攻撃者はGitHub Enterprise Serverインスタンス上でGitHub Pagesのサイトを作成して構築する権限を持っていなければなりません。この脆弱性は、GitHub Enterprise Serverのすべてのバージョンに影響します。この脆弱性を緩和するために、CVE-2020-14001への対応でkramdownがアップデートされました。 {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**高:** GitHub Enterprise Server上で実行されるGitのサブコマンドに、攻撃者が悪意ある引数をインジェクトすることができました。これによって、攻撃者は部分的にユーザが制御する内容で任意のファイルを上書きでき、GitHub Enterprise Serverインスタンス上で任意のコマンドを実行できる可能性がありました。この脆弱性を突くためには、攻撃者はGHESインスタンス内のリポジトリへのアクセス権限を持っていなければなりません。しかし、他の保護があるので、この脆弱性を積極的に突く方法は特定できませんでした。この脆弱性はGitHub Security Bug Bountyプログラムを通じて報告されました。{% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' bugs: - - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' - - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' - - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" - - 'Creating an issue on a user repository using the Issue Template feature could fail with an Internal Server Error. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' - - 'Visiting the *Explore* section failed with a 500 Internal Server error. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' - - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' - - 'Internal metrics gathering for background jobs contributed to CPU and memory use unnecessarily. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' - - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' - - 'Background jobs for an unreleased feature were queued and left unprocessed. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' + - 'Consulの設定エラーによって、スタンドアローンインスタンス上で処理されないバックグランドジョブがありました。{% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' + - 'サービスのメモリ割り当ての計算が、サービスに不正確もしくは無制限の割り当てを行い、システムのパフォーマンスを低下させることがありました。{% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' + - 'oVirt KVMシステムの可視化プラットフォームが適切に検出されず、アップグレードの際に問題を生じさせていました。{% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "Gitコマンドラインからのパスワードでの不正な認証のエラーメッセージが、適切なトークンもしくはSSHキーを追加するためのURLリンクを展開しませんでした。 {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" + - 'Issueテンプレート機能を使ってユーザリポジトリ上にIssueを作成すると、Internal Server Errorで失敗することがありました。 {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' + - '*Explore*セクションへのアクセスが500 Internal Server errorで失敗しました。{% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' + - '新しいインスタンスに移行したリポジトリ上で*最近の更新*でIssueをソートできませんでした。{% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'GitHub Connectが、非推奨のGitHub.com APIエンドポイントを使用していました。{% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'バックグラウンドジョブのための内部メトリクスの収集によって、不必要なCPUとメモリの使用に影響しました。{% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' + - '404ページのフッタに、GitHub.comの連絡先とステータスリンクが含まれていました。{% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' + - '未リリースの機能のためのバックグラウンドジョブがキューに積まれ、処理されないままになりました。{% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - - '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 %}' + - '監査ログは実際のソースIPアドレスの代わりに127.0.0.1に起因する可能性があります。(updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/5.yml b/translations/ja-JP/data/release-notes/2-21/5.yml index 6df83f51c2..fd93b35956 100644 --- a/translations/ja-JP/data/release-notes/2-21/5.yml +++ b/translations/ja-JP/data/release-notes/2-21/5.yml @@ -2,14 +2,14 @@ date: '2020-08-12' sections: bugs: - - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' - - 'Temporary connectivity issues while running database migrations could cause data loss. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' + - 'システム設定のテンプレートを生成する間にCPU使用率を高くしてしまうことがある問題を解決しました。{% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'メモリ割り当てへの最近の変更により、システムパフォーマンスが低下することがありました。{% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' + - 'データベースの移行を実行中の一時的な接続の問題によって、データの損失が生じることがあります。{% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - - '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 %}' + - '監査ログは実際のソースIPアドレスの代わりに127.0.0.1に起因する可能性があります。(updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/7.yml b/translations/ja-JP/data/release-notes/2-21/7.yml index bde6b2b9d3..52ebb3ddcc 100644 --- a/translations/ja-JP/data/release-notes/2-21/7.yml +++ b/translations/ja-JP/data/release-notes/2-21/7.yml @@ -2,13 +2,13 @@ date: '2020-09-08' sections: bugs: - - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + - 'サービスのへするチェックでセッションが増加し、ファイルシステムのinodeが枯渇しました。{% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "ホットパッチを使用したアップグレードが`'libdbi1' was not found`というエラーで失敗することがありました。{% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - - '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 %}' + - '監査ログは実際のソースIPアドレスの代わりに127.0.0.1に起因する可能性があります。(updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/8.yml b/translations/ja-JP/data/release-notes/2-21/8.yml index e99018a3fd..20d3a94bd4 100644 --- a/translations/ja-JP/data/release-notes/2-21/8.yml +++ b/translations/ja-JP/data/release-notes/2-21/8.yml @@ -2,15 +2,15 @@ date: '2020-09-23' sections: security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [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 %}' - - 'Packages have been updated to the latest security versions. {% 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 %}' + - '**中**: [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715)に対処するためにImageMagickがアップデートされました。{% comment %} https://github.com/github/enterprise2/pull/22621, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% 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: - - 'Admins were unable to see delivered repository webhooks and instead saw "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' + - '管理者は配信されたリポジトリのwebhookを見ることができず、代わりに"Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook"と表示されました。{% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - - '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 %}' + - '監査ログは実際のソースIPアドレスの代わりに127.0.0.1に起因する可能性があります。(updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/9.yml b/translations/ja-JP/data/release-notes/2-21/9.yml index 859227f743..a08e9685fb 100644 --- a/translations/ja-JP/data/release-notes/2-21/9.yml +++ b/translations/ja-JP/data/release-notes/2-21/9.yml @@ -2,28 +2,28 @@ date: '2020-10-09' sections: security_fixes: - - 'A user whose **LDAP** directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + - '**LDAP**ディレクトリのユーザ名を標準化すると既存のGHESアカウントのログインになってしまうユーザが、その既存のアカウントとして認証されることがありました。{% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' - - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' - - 'The enterprise account security settings page showed a "View your organizations'' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' - - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' - - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' - - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' + - '管理コンソールのNameID Fortmatドロップダウンが、"persistent"に設定された後に"unspecified"にリセットされます。{% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - '[管理コンソール](/admin/configuration/accessing-the-management-console) での設定の保存によって、[TLS/SSLの証明書及びキー](/admin/configuration/configuring-tls)ファイルに改行を追加してしまい、不必要に再ロードされるサービスが生じました。{% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - '依存関係グラフのシステムログがローテートされず、無制限にストレージを消費できてしまいました。{% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Resqueのワーカーのオーバーライドする設定が使われていると、アップグレードに失敗することがありました。{% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' + - '`ghe-migrator`でリポジトリをインポートする際に、不整合なデータが存在していると、予期しない例外が生じることがありました。{% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'GitHubセキュリティアドバイザリへのリンクが、GitHub.comではなくGitHub Enterprise Serverインスタンスのホスト名を持つURLを使い、ユーザを存在しないURLにアクセスさせました。{% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'エンタープライズアカウントのセキュリティ設定ページには、使用中の認証モードが二段階認証をサポートしていない場合、「組織の現在の設定を見る」リンクが表示されています。 {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' + - '`ghe-migrator`を使ってPRレビューリクエストをインポートする際に、削除されたユーザに関連付けられたレコードによって関係性を持たないデータベースレコードが残ります。{% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' + - '`ghe-migrator`でユーザをインポートする際に、システムによって生成されたメールアドレスが100文字以上の長さになっていると、"Emails is invalid"エラーが生じます。{% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'webhookのアクティビティのログが大量のディスク領域を使い、ルートディスクが一杯になってしまいます。{% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' changes: - - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + - 'AWS EC2のインスタンスタイプ`m5.16xlarge`のサポートが追加されました。{% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - '`ghe-migrator`アーカイブのSSHフィンガープリントはいつでも計算できるので、必須ではなくなりました。{% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub Appマニフェストに`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: - - '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 %}' + - '新たにセットアップされたユーザを持たない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 %}' - - '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 %}' + - '監査ログは実際のソースIPアドレスの代わりに127.0.0.1に起因する可能性があります。(updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-22/0.yml b/translations/ja-JP/data/release-notes/2-22/0.yml index 544ebbea80..11b2d9dc31 100644 --- a/translations/ja-JP/data/release-notes/2-22/0.yml +++ b/translations/ja-JP/data/release-notes/2-22/0.yml @@ -1,100 +1,100 @@ --- -intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. +intro: GitHubはGitHub Enterprise Server 2.22.0を紹介できることを嬉しく思います。 date: '2020-09-23' sections: features: - - heading: GitHub Actions Beta + heading: GitHub Actionsベータ notes: - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + [GitHub Actions](https://github.com/features/actions)は、CI/CDとワークフローの自動化のための強力で柔軟なソリューションです。Enterprise Server上のGitHub Actionsには、このサービスの管理を支援するツールが含まれており、ロールアウトの制御を支援するための管理コンソール内の主要なメトリクス、監査ログ、アクセス制御が含まれます。 - You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} + ユーザはGitHub Actionsのために自身の [ストレージ](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage)とランナーを提供しなければなりません。AWS S3、Azure Blob Storage、MinIOがサポートされています。GitHub Actionsを有効化する前に、[使用するプラットフォームのための最小の要件の更新](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance)をレビューしてください。さらに学ぶには、GitHubの営業チームに連絡するか、[ベータにサインアップ](https://resources.github.com/beta-signup/)してください。{% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - - heading: GitHub Packages Beta + heading: GitHub Packagesベータ notes: - | - [GitHub Packages](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](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + [GitHub Packages](https://github.com/features/packages)は、パッケージのホスティングサービスであり、GitHub API、Actions、webhookとネイティブに統合されています。コード、継続的インテグレーション、デプロイメントのソリューションを含む[エンドツーエンドのDevOpsワークフロー](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise)を作成してください。 - 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](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} + サポートされているストレージのバックエンドにはAWS S3とMinIOがあり、Azure blobのサポートも将来のリリースにあります。現在のDockerサポートは、次のリリースの新しいGitHub Container Registryで置き換えられることにご注意ください。GitHub Packagesを有効にする前に、[使用するプラットフォームの最小要件の更新](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance)をレビューしてください。さらに学ぶには、GitHubの営業チームに連絡するか、[ベータにサインアップ](https://resources.github.com/beta-signup/)してください。{% comment %} https://github.com/github/releases/issues/773 {% endcomment %} - - heading: Advanced Security Code Scanning Beta + heading: Advanced Security Code Scanningベータ notes: - | - [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. + [GitHub Advanced Security code scanning](https://github.com/features/security)は、開発者ファーストで、GitHubネイティブの静的アプリケーションセキュリティテスティング（SAST）です。脆弱性がプロダクションに到達してしまう前に容易に発見する、このすべてのパワーは世界で最も強力なコード解析エンジン、CodeQLによるものです。 - Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} + GitHub Advanced Security　を使用する管理者は、GitHub Advanced Security code scanningベータに[サインアップ](https://resources.github.com/beta-signup/)し、[有効化](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance)できます。GitHub Advanced Security code scanningを有効にする前に、[使用するプラットフォームの最小要件の更新](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance)をレビューしてください。{% comment %} https://github.com/github/releases/issues/768 {% endcomment %} - heading: Pull Request Retargeting notes: - | - When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} + [Pull Requestのheadブランチ](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)がマージされ、削除された場合、このブランチをターゲットとする同じリポジトリ内のすべての他のオープンなPull Requestは、マージされたPull Requestのベースブランチにターゲットし直されるようになりました。以前は、それらのPull Requestはクローズされていました。{% comment %} https://github.com/github/releases/issues/801 {% endcomment %} - - heading: Suspend and Unsuspend an App Installation + heading: アプリケーションのインストールのサスペンドとサスペンド解除 notes: - | - Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' + 管理者とユーザは、設定やAPIを通じてのコマンドで、必要な期間にわたって[任意のGitHub Appのアクセスをサスペンド](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation)したり、[アプリケーションのサスペンドを解除](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation)したりできます。サスペンドされたアプリケーションは、GitHub APIあるいはwebhookイベントにアクセスできません。これは、すべてのユーザの認可を解除してしまうアプリケーションのアンインストールの代わりに利用できます。{% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' - - heading: Improved Large Scale Performance + heading: 改善された大規模でのパフォーマンス notes: - | - We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% 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 %}'' + リポジトリのネットワークメンテナンスのスケジューリングアプローチを見直し、大きな単一リポジトリが障害の状態になるのを避けられるようにしました。{% 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 %}'' - Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} + パッシブレプリカが[GitHub Enterprise Serverクラスタデプロイメントをサポートし、設定可能に]なりました(https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster)。これらの変更によって、高速なフェイルオーバー、RTOとRPOの削減が可能になりました。{% comment %} https://github.com/github/releases/issues/905 {% endcomment %} - - heading: View All of Your Users + heading: すべてのユーザの表示 notes: - | - For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](https://docs.github.com/en/enterprise/2.22/admin/configuration/command-line-utilities#ghe-config). {% comment %} https://github.com/github/github/pull/146508 {% endcomment %}'' + 例外的に大きなTeamの場合、管理者は[ユーザリストのデフォルトの最大数の1,500を調整](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: Administration Changes + heading: 管理に関する変更 notes: - - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} - - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} - - 'It''s now possible to [manage global announcements and expiration dates through the enterprise account settings](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 %}' - - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} - - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} - - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% 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 %} - - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} - - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} - - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% 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 %}' + - 共有ワーカーは、タブ間で接続を共有することによって、ライブアップデートにより弾力性を持たせることができるようになりました。{% comment %} https://github.com/github/releases/issues/914 {% endcomment %} + - '`50x`エラーページの"Contact Support"リンクは、サポートのメールもしくは管理コンソールで設定されたリンクにリンクされるようになりました。{% comment %} https://github.com/github/github/pull/142123 {% endcomment %}' + - '[Enterpriseアカウント設定を通じて、グローバルなアナウンスと有効期限を管理]できるようになりました。(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 %}' + - 必要な場合、[管理コンソールで設定されたデフォルトのAPIのレート制限から、特定のユーザを除外](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits)できるようになりました。{% comment %} https://github.com/github/github/pull/148673 {% endcomment %} + - リポジトリ管理者は、リポジトリ設定の単一のダイアログから[自分のリポジトリを利用可能な任意の可視性のオプションに設定](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility)できるようになりました。以前は、パブリックとプライベート間、そしてプライベートとインターナル間の変更には、個別のセクション、ボタン、ダイアログボックスを使わなければなりませんでした。{% comment %} https://github.com/github/releases/issues/882 {% endcomment %} + - ユーザのドロップダウンメニュー上の新しいEnterprise設定のリンクによって、Enterpriseアカウント設定へのアクセスが容易になりました。{% 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 %} + - /stafftoolsページにあった旧来の"Admin Center"リンクは削除されました。/stafftoolsページからEnterpriseアカウントにアクセスする最善の方法は、"Enterprise"リンクになりました。{% comment %} https://github.com/github/github/pull/147633 {% endcomment %} + - Enterpriseアカウント設定のOptionsサブメニューアイテムは、SettingsセクションからPoliciesセクションへ移されました。{% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} + - '[個人アクセストークンもしくはSSHキーを使ったリソースへのアクセスは、ユーザのアクティビティとしてカウントされるようになりました](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users)。これで、管理者はユーザの休止レポートから特定のユーザをフィルタリングしなくてもよくなり、個人アクセストークン（PAT）あるいはSSHキーでAPIを通じて読み取りのみでGitHubにアクセスしているだけのユーザをうっかりサスペンドしてしまうことなく、安全に"Suspend all"ボタンを使えるようになります。{% 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: Security Changes + heading: セキュリティの変更 notes: - - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} - - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](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 %} - - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} + - 2要素のリカバリコードは、2要素でのサインインのプロセス中には使えなくなりました。受け付けられる値はワンタイムパスワードのみです。{% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} + - ユーザがシングルサインオンを通じてGitHub Enterprise Serverにサインインする際に、[デフォルトのリポジトリの可視性の選択はプライベートになります](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 %} + - GitHub Appのオーナーは、[ユーザからサーバーへのアクセストークンが8時間で期限切れになる](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/)よう選択して、定期的なトークンのローテーションを強制しやすくし、侵害されたトークンの影響を軽減できるようになりました。{% comment %} https://github.com/github/releases/issues/966 {% endcomment %} - - heading: Developer Changes + heading: 開発者の変更 notes: - - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' - - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} - - 'Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' - - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} - - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' + - '[GitHubのUIは設計しなおされ](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/),、リポジトリのホームページも、レスポンシブなレイアウトや改善されたモバイルのWeb体験を含め、再設計されました。{% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' + - リポジトリの"Clone with SSH"ドロップダウンメニューで、キーをセットアップしていないことがユーザに通知されるようになりました。{% comment %} https://github.com/github/github/pull/149098 {% endcomment %} + - 'Pull Requestタイムライン及びコミットタブ内で、コミットが時系列で並べられるようになりました。この新しい順序は["Pull Request上のコミットのリスト"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API及びGraphQLの["PullRequestオブジェクト"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest)のタイムラインコネクションにも反映されます。{% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' + - ユーザは、コメントのテキスト領域で[絵文字のオートコンプリートの結果のためのスキントーンのデフォルトを設定](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/)できるようになりました。{% comment %} https://github.com/github/releases/issues/916 {% endcomment %} + - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter)は、構文ハイライトを改善し、言語のパースに使われるデフォルトのライブラリになりました。{% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' - - heading: Users and organizations can add Twitter usernames to their GitHub profiles + heading: ユーザとOrganizationは、GitHubのプロフィールにTwitterのユーザ名を追加できるようになりました。 notes: - - '[Developers and organizations can now add their Twitter username to their profile](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 %}' + - '[開発者とOrganizationは、プロフィールに自分のTwitterユーザ名を追加できるようになりました](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: API の変更 notes: - | - #### Graduated Previews + #### プレビューからの卒業 - The following previews are now an official part of the API: - * The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} - * To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} + 以下のプレビューは、APIの公式部分になりました。 + * `performed_via_github_app`属性を返すGitHub Apps APIとエンドポイントは、 [`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 %} + * Issueにロックの理由を追加して表示するために、[`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 %} - | - #### GraphQL Schema Changes + #### GraphQLのスキーマ変更 - * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + * [GraphQLのスキーマ変更](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog)には、後方互換な変更、スキーマのプレビュー、今後の破壊的変更が含まれます。 - - heading: VMware Network Driver Changes + heading: VMwareのネットワークドライバの変更 notes: - | - The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: + VMwareの顧客のためのGitHub Enterprise Serverのデフォルトネットワークアダプタの種類は、リリース2.22.0よりE1000からVMXNET3に変更されました。以前のリリースから2.22.0移行へアップグレードする際に、アップグレード前のチェックの間にE1000ネットワークアダプタが検出されると、以下のメッセージがコマンドラインに表示されます。 ``` WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. @@ -102,42 +102,42 @@ sections: Proceed with installation? [y/N] ``` - The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} + 管理者は、GitHub Enterprise Serverのアップグレードの前後のいずれかで、ネットワークアダプタの種類をVMXNET3に更新することを選択できます。この変更を行うためには、仮想アプライアンスをシャットダウンする必要があります。お客様はVMXNET3への[仮想マシンのネットワークアダプタ設定の変更](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html)の推奨手順に従ってください。仮想アプライアンスのOSバージョンが`Other Linux (64-bit)`に設定されている場合、`VMXNET3`は選択肢にならないことに注意してください。その場合は、OSバージョンをまず`Other Linux (64-bit)`から`Other 2.6.x Linux (64-bit)`へ、もしくは可能であれば`Debian GNU/Linux 9`に変更する必要があります。これらの変更は、プロダクションのGitHub Enterprise Serverで行う前に、[ステージングのインスタンス](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance)でテストすることをおすすめします。{% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} bugs: - - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} - - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} - - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} - - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} + - 保留中のメール招待があると、保留中のコラボレータを表示するためのstafftoolsページが`500 Internal Server Error`を表示しました。{% comment %} https://github.com/github/github/pull/150836 {% endcomment %} + - stafftools中のリポジトリヘルスチェックが、高負荷のリポジトリで不正確な結果を返すことがありました。{% comment %} https://github.com/github/github/pull/151160 {% endcomment %} + - メールの招待を受諾しようとするログインユーザに`404 Not Found`エラーが返されることがありました。{% comment %} https://github.com/github/github/pull/150848 {% endcomment %} + - 名前が"repositories."で始まるリポジトリにユーザがアクセスしようとすると、リポジトリの概要ページの代わりにオーナーの"Repositories"タブにリダイレクトされました。{% comment %} https://github.com/github/github/pull/149704 {% endcomment %} + - ダッシュボードタイムラインのラベルが十分なコントラストを持っていませんでした。{% comment %} https://github.com/github/github/pull/146749 {% endcomment %} deprecations: - - heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 + heading: GitHub Enterprise Server 2.19の非推奨の予定 notes: - - '**GitHub Enterprise Server 2.19 will be 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 GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - '** GitHub Enterprise Server 2.19は2020年11月12日に非推奨となります** これは、この日以降は重大なセキュリティの問題に対してであってもパッチリリースが行われなくなるということです。より優れたパフォーマンス、改善されたセキュリティ、新しい機能のために、[GitHub Enterprise Serverの最新バージョンへのアップグレード](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/)をできるだけ早く行ってください。' - - heading: Deprecation of Legacy GitHub App Webhook Events + heading: 旧来のGitHub App webhookイベントの非推奨化 notes: - - 'Starting with GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.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/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - 'GitHub Enterprise Server 2.21.0から、2つの旧来のGitHub Appsに関連するwebhookイベントが非推奨となり、GitHub Enterprise Server 2.25.0で削除されます。非推奨となったイベントの`integration_installation`と`integration_installation_repositories`には、サポートされることになる同等のイベントがあります。詳細な情報は[非推奨化のアナウンスのblogポスト](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: Deprecation of Legacy GitHub Apps Endpoint + heading: 旧来のGitHub Appsのエンドポイントの非推奨化 notes: - - 'Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.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/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - 'GitHub Enterprise Server 2.21.0から、インストールアクセストークンを作成するための旧来のGitHub Appsのエンドポイントが非推奨になり、GitHub Enterprise Server 2.25.0で削除されます。詳細な情報は[非推奨化のアナウンスのblogポスト](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: Deprecation of OAuth Application API + heading: OAuth Application APIの非推奨化 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 GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + - GitHubは、パスパラメータとして`access_token`を含むOAuthのアプリケーションエンドポイントをサポートしなくなりました。`access_token`をリクエストのボディに移すことにより、OAuth Appsのためのトークンをセキュアに管理できるようにする、新しいエンドポイントが導入されます。非推奨にはなりましたが、これらのエンドポイントはこのバージョンではまだ利用可能です。これらのエンドポイントは、GitHub Enterprise Server 3.4で削除しようとしています。詳細については[非推奨化のアナウンスのblogポスト](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/)を参照してください。 backups: - - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + - GitHub Enterprise Serverでは、[バックアップとディザスタリカバリー](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/)のために、最低でも[GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0が必要です。 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 %} - - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} - - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} - - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} - - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a 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 %}' - - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} - - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% 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 %} + - 新たにセットアップされたユーザを持たない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 %} + - 管理コンソールのName ID Fortmatドロップダウンが、インスタンスを"persistent"に設定した後に"unspecified"にリセットされます。{% comment %} https://github.com/github/enterprise2/issues/13446{% endcomment %} + - ユーザもしくはOrganizationのGitHub Pagesサイトのためのリポジトリの設定ページが"500 Internal Server Error"で失敗します。{% comment %} https://github.com/github/github/issues/156183 {% endcomment %} + - 読み取りが他のノードに転送されるため、High Availabilityのレプリカのインスタンスで、Gitのクローン及びフェッチのパフォーマンスが低下することがあります。{% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} + - '[マニフェストからのGitHub Appの作成](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest)が失敗します。この問題を回避するために、ユーザは[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 %}' + - SAML認証を使っていて、GitHubのユーザ名が管理コンソールの`username`フィールドにマップされた属性の値と一致しない場合に、GitHubのユーザ名が意図せずに変更されてしまうことがあります。{% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} + - 新たにセットアップされた2.22.0のインスタンス、もしくは2.22.0へのアップグレード後、Organizationのダッシュボード上のアクティビティフィードが更新されなくなります。（2020-10-27更新）{% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - 監査ログは実際のソースIPアドレスの代わりに127.0.0.1に起因する可能性があります。(updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/2-22/1.yml b/translations/ja-JP/data/release-notes/2-22/1.yml index 8edfa619f0..257a013bab 100644 --- a/translations/ja-JP/data/release-notes/2-22/1.yml +++ b/translations/ja-JP/data/release-notes/2-22/1.yml @@ -2,70 +2,70 @@ date: '2020-10-09' sections: security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [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 %}' - - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' - - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + - '**中**: [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715)に対処するためにImageMagickがアップデートされました。{% comment %} https://github.com/github/enterprise2/pull/22623, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' + - 'OAuthアクセストークンをリフレッシュするためのGitHub Appのインテグレーションからのリクエストが、リフレッシュトークンを作成するのに使われたものとは異なる、有効なOAuthクライアントIDとクライアントシークレットで送信された場合に受け付けられます。{% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' + - 'LDAPディレクトリのユーザ名を標準化すると既存のGHESアカウントのログインになってしまうユーザが、その既存のアカウントとして認証されることがありました。{% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' bugs: - | - The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} + 管理コンソールのNameID Fortmatドロップダウンが、"persistent"に設定された後に"unspecified"にリセットされます。{% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} - | - Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} + ホットパッチを使用したアップグレードが`'libdbi1' was not found`というエラーで失敗することがありました。{% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - | - Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + [管理コンソール](/admin/configuration/accessing-the-management-console) での設定の保存によって、[TLS/SSLの証明書及びキー](/admin/configuration/configuring-tls)ファイルに改行を追加してしまい、不必要に再ロードされるサービスが生じました。{% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - | - System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} + 依存関係グラフのシステムログがローテートされず、無制限にストレージを消費できてしまいました。{% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - | - The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} + MS SQL Serverのパフォーマンスグラフは、レプリカが選択されている場合でも、インスタンスからの統計を表示します。{% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} - | - `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} + `ghe-actions-precheck`は、Actionsが有効化されていない場合、ストレージチェックを実行せず、何も示さずに終了してしまいます。{% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} - | - Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} + Resqueのワーカーのオーバーライドする設定が使われていると、アップグレードに失敗することがありました。{% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} - | - Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} + コンテナ内で実行されるサービスに、ログをジャーナルに送信しないものがありました。{% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} - | - Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} + GitHubセキュリティアドバイザリへのリンクが、GitHub.comではなくGitHub Enterprise Serverインスタンスのホスト名を持つURLを使い、ユーザを存在しないURLにアクセスさせました。{% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} - | - When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} + `ghe-migrator`でリポジトリをインポートする際に、不整合なデータが存在していると、予期しない例外が生じることがありました。{% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} - | - The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} + Enterpriseアカウントのセキュリティ設定ページは、使用されている認証モードがビルトインの2要素認証をサポートしていない場合、"Two-factor authentication"設定に対して"View your organizations' current configurations"リンクを表示しました。{% comment %} https://github.com/github/github/pull/153860 {% endcomment %} - | - OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} + OAuthリフレッシュトークンは、早期に削除されます。{% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} - | - Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} + 検索の修復タスクは、設定の移行フェーズの間に例外を生成します。{% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} - | - On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} + 環境によって、GitHub Appsの設定ページで"Beta Features"が表示されませんでした。{% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} - | - When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} + `ghe-migrator`を使ってPRレビューリクエストをインポートする際に、削除されたユーザに関連付けられたレコードによって関係性を持たないデータベースレコードが残ります。{% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} - | - When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} + `ghe-migrator`でユーザをインポートする際に、システムによって生成されたメールアドレスが100文字以上の長さになっていると、"Emails is invalid"エラーが生じます。{% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} - | - Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} + webhookのアクティビティのログが大量のディスク領域を使い、ルートディスクが一杯になってしまいます。{% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} - | - Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} + 読み取りが他のノードに転送されるため、High Availabilityのレプリカのインスタンスで、Gitのクローン及びフェッチのパフォーマンスが低下しました。{% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} - | - The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} + ユーザもしくはOrganizationのGitHub Pagesサイトのためのリポジトリの設定ページが"500 Internal Server Error"で失敗します。{% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} - | - Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} + リポジトリネットワークのメンテナンス操作が、`running`の状態で停止することがありました。{% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} - | - A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} + コードスキャンニングの結果のアップロードの直後に1つのリポジトリを削除すると、すべてのリポジトリのコードスキャンニングの結果の処理が停止することがありました。{% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} - | - When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} + 同時に大量のコードスキャンニングの結果がサブミットされると、バッチの処理がタイムアウトし、コードスキャンニングの結果の処理が停止することがありました。{% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} - | - [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} + [マニフェストからのGitHub Appsの作成](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest)が失敗します。{% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} - | - GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management Console. {% comment %} https://github.com/github/github/pull/158131, https://github.com/github/github/pull/157936, https://github.com/github/external-identities/issues/335 {% endcomment %} + SAML認証を使っていて、GitHubのユーザ名が管理コンソールの`username`フィールドにマップされた属性の値と一致しない場合に、GitHubのユーザ名が意図せずに変更されてしまいました。{% 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: - - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} - - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} - - GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156991, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %} + - AWS EC2のインスタンスタイプ`m5.16xlarge`のサポートが追加されました。{% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} + - '`ghe-migrator`アーカイブのSSHフィンガープリントはいつでも計算できるので、必須ではなくなりました。{% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %}' + - GitHub Appマニフェストに`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: - - 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 %} - - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} - - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% 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 %} + - 新たにセットアップされたユーザを持たない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 %} + - 元々のバックアップソースでGitHub Actionsが有効化されていなかった場合に、データをGitHub Actionsが有効化されているインスタンスにリストアすると、設定の更新に失敗します。{% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} + - "2.22.0を実行しているインスタンスで以前にGitHub Actionsが有効化されており、2.22.1へアップグレードすると、GitHub Actionsの起動に失敗することがあります。（2020-10-23更新）\n{% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}" + - 新たにセットアップされた2.22.1のインスタンス、もしくは2.22.1へのアップグレード後、Organizationのダッシュボード上のアクティビティフィードが更新されなくなります。（2020-10-27更新）{% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - 監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。（2020-11-02更新）{% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/2-22/2.yml b/translations/ja-JP/data/release-notes/2-22/2.yml index dc36b39e12..89790a644f 100644 --- a/translations/ja-JP/data/release-notes/2-22/2.yml +++ b/translations/ja-JP/data/release-notes/2-22/2.yml @@ -2,28 +2,28 @@ date: '2020-10-20' sections: security_fixes: - - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} + - パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} bugs: - | - If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} + GitHub Actionsの設定中にストレージアカウント設定の検証に失敗した場合、新たに試行する前に`ghe-actions-teardown`の実行が必要でした。{% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} - | - A custom proxy configuration could adversely affect the GitHub Actions environment. {% 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 %} + カスタムのプロキシ設定が、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 %} - | - On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} + eth0のアドレス変更時に、Nomad及びConsulがレスポンスを返さなくなることがありました。{% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} - | - When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} + 自己署名証明書を使用した場合、GitHub Actionsの設定の際にGHESがSSL検証の例外を起こすことがありました。{% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} - | - Using a GitHub Action from a branch name with a `+` or `/` character resulted in an 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 %} + `+`あるいは`/`キャラクタをブランチ名に含むブランチからGitHub Actionを利用すると、`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 %} - | - The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} + Enterpriseアカウントの"Confirm two-factor requirement policy"メッセージが正しくありませんでした。{% comment %} https://github.com/github/github/pull/158735 {% endcomment %} - | - On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} + 100MBを超える特定のリクエストで、Kafkaのバッファが過剰に割り当てられることがありました。{% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% 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 %} - - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% 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 %} + - 新たにセットアップされたユーザを持たない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 %} + - "2.22.0を実行しているインスタンスで以前にGitHub Actionsが有効化されており、2.22.2へアップグレードすると、GitHub Actionsの起動に失敗することがあります。（2020-10-23更新）\n{% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}" + - 新たにセットアップされた2.22.2のインスタンス、もしくは2.22.2へのアップグレード後、Organizationのダッシュボード上のアクティビティフィードが更新されなくなります。（2020-10-27更新）{% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - 監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。（2020-11-02更新）{% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/2-22/3.yml b/translations/ja-JP/data/release-notes/2-22/3.yml index 45442a5d4b..c59ed7ea46 100644 --- a/translations/ja-JP/data/release-notes/2-22/3.yml +++ b/translations/ja-JP/data/release-notes/2-22/3.yml @@ -3,21 +3,21 @@ date: '2020-11-03' sections: security_fixes: - | - **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} + **低:** SVNブリッジへの特別に細工されたリクエストによって引き起こされる高いCPU使用率によって、SVNブリッジサービスでサービス拒否（DoS）が引き起こされる可能性がありました。（2020-11-16更新）{% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} - | - **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} + **低:** 不正確なトークンの検証によって、認証中のトークンのマッチのためのエントロピーが減少しました。分析からは、実際には大きなセキュリティ上のリスクはないことが示されています。{% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} - | - Packages have been updated to the latest security versions. {% 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 %} + パッケージが最新のセキュリティバージョンに更新されました。{% 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: - - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 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 %} - - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} - - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} - - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} - - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} + - 2.22.0を実行しているインスタンスで以前にGitHub Actionsが有効化されており、2.22.1もしくは2.22.2へアップグレードすると、GitHub Actionsの起動に失敗することがあります。{% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - High Availabilityのレプリカをセットアップする際に、GitHub Actionsの設定ファイルがレプリカにコピーされず、そのために`ghe-repl-promote`の間にエラーが生じる可能性があります。{% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} + - 新たにセットアップされた2.22.1あるいは2.22.2のインスタンス、もしくは2.22.1あるいは2.22.2へのアップグレード後、Organizationのダッシュボード上のアクティビティフィードが更新されなくなります。{% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} + - 非ASCIIキャラクタを含むファイル名のIssueテンプレートを編集すると、"500 Internal Server Error"で失敗します。{% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} + - バックグラウンドジョブのメトリック収集方式のために、CPU使用率が増大しました。（2020-11-03更新）{% comment %} https://github.com/github/github/pull/160109 {% 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 %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% 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 %} + - 監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。（--更新）{% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/2-22/4.yml b/translations/ja-JP/data/release-notes/2-22/4.yml index e97737ee0b..0fb3aa956a 100644 --- a/translations/ja-JP/data/release-notes/2-22/4.yml +++ b/translations/ja-JP/data/release-notes/2-22/4.yml @@ -2,15 +2,15 @@ date: '2020-11-17' sections: security_fixes: - - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} + - パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} bugs: - - The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} - - After upgrading GHES with a hotpatch, the `ghe-actions-precheck` and `ghe-packages-precheck` commands would fail with the error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} - - When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} - - Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} + - baneldログに秒とマイクロ秒の間のセパレータが欠けていました。 {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} + - ホットパッチでGHESをアップグレードした後、`ghe-actions-precheck`及び`ghe-packages-precheck`コマンドが`"docker load" accepts no arguments`というエラーで失敗します。{% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} + - Enterpriseアカウントの"Repository visibility change"ポリシーが"Enabled"に設定されている場合、OrganizationオーナーがOrganization内のリポジトリの可視性を変更できませんでした。 {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} + - 監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。{% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% 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 %} + - 新たにセットアップされたユーザを持たない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 %} diff --git a/translations/ja-JP/data/release-notes/2-22/5.yml b/translations/ja-JP/data/release-notes/2-22/5.yml index 0520df862f..ef3cf7dcb0 100644 --- a/translations/ja-JP/data/release-notes/2-22/5.yml +++ b/translations/ja-JP/data/release-notes/2-22/5.yml @@ -2,21 +2,21 @@ date: '2020-12-03' sections: bugs: - - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' - - 'The Elasticsearch upgrade process was not getting captured by ghe-diagnostics. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' - - 'Enabling GitHub Actions on an upgraded high availability configuration caused errors in replication. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' - - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' - - 'Users connecting to an active replica would get an error connecting to the live updates websocket. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' - - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% 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 %}' - - 'For GHES instances using built-in authentication with an internal SAML identity provider, users without an associated email address could not create a commit from the web interface. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' + - 'ブートストラップ時のレース条件により、認可サービスが不健全として検出され、再起動されることにつながりました。{% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' + - 'Elasticsearchのアップグレードのプロセスが、ghe-diagnosticsに捉えられませんでした。{% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' + - 'アップグレードされたHigh Availability設定でGitHub Actionsを有効化すると、レプリケーションでエラーが生じました。{% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' + - '下位の動作により、ホットパッチアップグレードのプロセス中に、サービスが利用できなくなりました{% comment %} https://github.com/github/enterprise2/pull/24055, {% endcomment %}' + - 'アクティブなレプリカに接続するユーザに、ライブアップデートのwebsocketへの接続でエラーが返されます。{% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' + - 'ログ転送SSL証明書の一部が正しく適用されませんでした。{% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'サスペンドされたユーザがTeamあるいはOrganizationから削除されると、そのユーザにメール通知が送信されました。{% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'SSH証明書の適用方法が、OrganizationとBusiness間で整合していませんでした。{% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - '不正確なパスワードの利用のためにアカウントにレート制限が適用された場合に、最大で24時間ロックアウトされることがありました。{% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - '多くの参照を持つリポジトリ上のPull Requestの同期が、ワーカーキューを遅れさせることがありました。{% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' + - '特定のページへのアクセスを試みた後にサインインすると、意図したアクセス先ではなくホームページにユーザが送られてしまいました。{% 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 %}' + - 'ビルトインの認証を内部的なSAMLアイデンティティプロバイダで利用しているGHESインスタンスにおいて、関連づけられたメールアドレスのないユーザは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: - - '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 %}' + - '新たにセットアップされたユーザを持たない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 %}' diff --git a/translations/ja-JP/data/release-notes/2-22/6.yml b/translations/ja-JP/data/release-notes/2-22/6.yml index 971924052f..009bdd0845 100644 --- a/translations/ja-JP/data/release-notes/2-22/6.yml +++ b/translations/ja-JP/data/release-notes/2-22/6.yml @@ -2,17 +2,17 @@ date: '2020-12-17' sections: security_fixes: - - '**LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1022, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/24353, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' + - '**低:** SVNブリッジへの特別に細工されたリクエストによって引き起こされる高いCPU使用率によって、サービス拒否（DoS）が引き起こされる可能性がありました。{% comment %} https://github.com/github/slumlord/pull/1022, https://github.com/github/slumlord/pull/1017 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/24353, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' bugs: - - 'Requests for some file resources like a zip archive or raw file could enter a redirection loop. {% comment %} https://github.com/github/enterprise2/pull/24193, https://github.com/github/enterprise2/pull/24075 {% endcomment %}' - - 'A timeout could prevent some Issues and Pull Requests searches from providing complete search results. {% comment %} https://github.com/github/github/pull/164155, https://github.com/github/github/pull/163845 {% endcomment %}' - - 'Custom tabs with non-alphabetic characters in small screens did not render correctly. {% comment %} https://github.com/github/github/pull/164310, https://github.com/github/github/pull/164159 {% endcomment %}' - - 'An underlying behavior was causing failures when pushing content to a Git LFS-enabled repository. {% comment %} https://github.com/github/github/pull/164663, https://github.com/github/github/pull/150179 {% endcomment %}' - - 'In some rare cases issues could cause a 500 error when accessed via the web interface. {% comment %} https://github.com/github/github/pull/165298, https://github.com/github/github/pull/159674 {% endcomment %}' + - 'zipアーカイブや生のファイルのような、一部のファイルリソースに対するリクエストがリダイレクトのループに入ってしまうことがありました。{% comment %} https://github.com/github/enterprise2/pull/24193, https://github.com/github/enterprise2/pull/24075 {% endcomment %}' + - 'タイムアウトによって、一部のIssueやPull Requestの検索が完全な検索結果を返せないことがありました。{% comment %} https://github.com/github/github/pull/164155, https://github.com/github/github/pull/163845 {% endcomment %}' + - '小さな画面で、非アルファベットの文字を含むカスタムタブが、正しく表示されませんでした。{% comment %} https://github.com/github/github/pull/164310, https://github.com/github/github/pull/164159 {% endcomment %}' + - '下位の動作によって、Git LFSが有効化されたリポジトリへのコンテンツのプッシュが失敗していました。{% comment %} https://github.com/github/github/pull/164663, https://github.com/github/github/pull/150179 {% endcomment %}' + - 'Webインターフェース経由でのアクセスの際に、まれな状況で問題が生じて500エラーになることがありました。{% comment %} https://github.com/github/github/pull/165298, https://github.com/github/github/pull/159674 {% 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 %}' + - '新たにセットアップされたユーザを持たない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 %}' diff --git a/translations/ja-JP/data/release-notes/3-0/0-rc1.yml b/translations/ja-JP/data/release-notes/3-0/0-rc1.yml index 99429fc282..eebf37a1fd 100644 --- a/translations/ja-JP/data/release-notes/3-0/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/3-0/0-rc1.yml @@ -1,145 +1,145 @@ --- date: '2021-01-12' release_candidate: true -intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)". +intro: リリース候補バージョンは、非プロダクション環境でテストすべきです。リリース候補プログラムに関する詳しい情報については、[GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) もしくは[新リリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-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. + [{% data variables.product.prodname_actions %}](https://github.com/features/actions)は{% data variables.product.prodname_ghe_server %} 3.0以降で一般に利用可能になりました。{% data variables.product.prodname_dotcom %}からコードをビルド、テスト、デプロイしてください。コードレビューのサブミット、ブランチ管理、Issueのトリアージ作業を好きな方法で行ってください。 - This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + このリリースには、{% data variables.product.prodname_ghe_server %}上の{% data variables.product.prodname_actions %}のベータからのいくつかの改善が含まれています。 - - 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. + - Enterprise、Organization、リポジトリの管理者は、{% data variables.product.prodname_dotcom_the_website %}上の{% data variables.product.prodname_actions %}へのアクセスに対するセキュリティポリシーを作成できます。 + - Enterprise、Organization、リポジトリの管理者は、パブリックリポジトリで瀬フルホストランナーの利用を許可できます。 + - Enterprise、Organization、リポジトリの管理者はワークフローを[プライベートリポジトリのフォークから上がってきたPull Requestに対して実行](/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)することを許可できるようになりました。 + - `workflow_run`イベントが「サポートされました](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run)。 + - ユーザは[ワークフローを無効化し、後日有効化](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)できるようになりました。 + - ワークフローのログが[ユーザ体験を改善する](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs)ために拡張されました。 + - ユーザは、コンテナジョブとサービスでプライベートのイメージを使えるようになりました。 + - [成果物とログの最大の保持日数がカスタマイズできるようになりました](/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)。 + - ランナーグループAPIに[labels]が含まれるようになりました(/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)。 + - 実行ステップを組み合わせてシェルスクリプトを使い、再利用可能なアクションを作成できるようになりました。 + - [Organizationのための暗号化されたシークレット](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)によって、リポジトリ間にわたるシークレットをまとめられるようになりました。 + - [Organizationのためのワークフローテンプレート](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization)によって、Organizationに渡るベストプラクティスと一貫性がスムーズになり、推進されます。 - {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + 現時点で、クラスタ設定を使用するEnterpriseでは{% data variables.product.prodname_actions %}はサポートされません。 - heading: GitHub Packages 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. + {% data variables.product.prodname_registry %}(https://github.com/features/packages)はパッケージホスティングサービスで、GitHub API、Actions、webhookとネイティブに統合されています。コード、継続的インテグレーション、デプロイメントのソリューションを含む[エンドツーエンドのDevOpsワークフロー](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise)を作成してください。 - 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 %}. + サポートされるストレージのバックエンドにはAWS S3とMinIOが含まれ、将来のリリースでAzure blobもやってきます。現在のDockerサポートは、次のリリースの新しいGitHub Container Registryのベータで置き換えられることに注意してください。{% data variables.product.prodname_registry %}を有効にする前に、[プラットフォームの最小要件の更新](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance)をレビューしてください。 - 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) + パッケージをNuGetに公開する際に、ユーザは認証トークンをファイルに書く代わりに`--api-key`オプションを使って渡せるようになりました。詳しい情報については[GitHub Packagesで使うためのdotnet CLIの設定](/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. + 現時点で、クラスタ構成を使用するEnterpriseでは{% data variables.product.prodname_registry %}はサポートされていません。 - - heading: GitHub Mobile beta + heading: GitHub Mobileベータ 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 %}](https://github.com/features/)ベータを利用すれば、自分のデバイスから通知をトリアージし、IssueやPull Requestを管理できるようになります。モバイルには、{% data variables.product.prodname_dotcom_the_website %}上の1つのユーザアカウントと、{% data variables.product.prodname_ghe_server %}上の1つのユーザアカウントで同時にサインインできます。 - {% 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`. + {% data variables.product.prodname_mobile %}ベータは、{% data variables.product.prodname_ghe_server %}で利用できるようになりました。[Android](https://play.google.com/store/apps/details?id=com.github.android)と[iOS](https://apps.apple.com/app/github/id1477376905)のアプリケーションでサインインして、外出先で通知をトリアージし、IssueとPull Requestを管理してください。管理者は管理コンソールを使って、あるいは`ghe-config app.mobile.enabled false`を実行して、Enterpriseのモバイルサポートを無効化できます。 - - heading: Advanced Security Secret Scanning beta + heading: Advanced Security Secret Scanningベータ 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. + [Secret Scanningベータ](https://github.com/features/security)は、コミットされた認証情報をパブリック及びプライベートのリポジトリでスキャンし、シークレットを見つけ、それらがリポジトリにコミットされたときにシークレットの提供者あるいは管理者に通知します。 - 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. + {% data variables.product.prodname_GH_advanced_security %}を利用する管理者は、{% data variables.product.prodname_GH_advanced_security %} Secret Scanningを[有効化し、設定](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance)できます。{% data variables.product.prodname_GH_advanced_security %} Secret Scanningを有効化する前に、[プラットフォームの最小要件の更新](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance)をレビューできます。 - 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)" + [GitHub Advanced Security code scanning](https://github.com/features/security)は、GitHub Enterprise Serverで一般に利用可能になりました。Advanced Securityを購入したOrganizationは、この機能を使って静的解析のセキュリティテストをコードに対して行い、私たちのセマンティック解析エンジンであるCodeQLを使って脆弱性がプロダクションコードにまで及ぶことを回避できます。詳しい情報については「[アプライアンス上でのcode scanningの設定](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)」を参照してください。 changes: - - heading: Administration Changes + heading: 管理に関する変更 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. + - 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)できるようになりました。' + - 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: Security Changes + heading: セキュリティの変更 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. + - Organizationのオーナーは、Organization内のリポジトリからの{% data variables.product.prodname_pages %}サイトの公開を無効化できるようになりました。Organizationの{% data variables.product.prodname_pages %}を無効化すると、メンバーは新しいPagesのサイトを作成できなくなりますが、既存のサイトの公開は取り消されません。詳しい情報については「[Organizationでの{% data variables.product.prodname_pages %}サイトの公開の無効化](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)」を参照してください。 + - アクティブなレプリカを有効化する前に、すべてのノードでデータセンターは明示的に定義されていなければなりません。 + - SSHフィンガープリントのすべての利用は、バージョン6.8以降のOpenSSHで使われているのと同様に、SHA256を使うように切り替えられました。これは、Webのインターフェースに適用されると共に、GraphQLのようにフィンガープリントを返すAPIにも適用されます。フィンガープリントは、OpenSSHのフォーマットに従います。 + - SHA-1及びSHA-256の署名ヘッダ（2つのヘッダ）は、webhook上で送信されます。 - - heading: Developer Changes + heading: 開発者の変更 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. + - '{% data variables.product.prodname_ghe_server %} 3.0以降で動作しているサービスの大部分はコンテナ上に置かれるようになり、内部的にGitHubが反復を早め、高品質なリリースを行えるようにしています。' + - webhookイベントの配信システムは、高いスループット、高速な配信、遅延するメッセージの減少のために、再設計されました。 - heading: 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)."' + - '管理者は、REST APIを通じてサイト全体のアナウンスのバナーを設定し、管理できるようになりました。詳しい情報については「[GitHub Enterpriseの管理](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)」のエンドポイントを参照してください。' - - heading: Default branch renaming + heading: デフォルトブランチの名称変更 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. + Enterprise及びOrganizationの管理者は、新しいリポジトリのためのデフォルトブランチ名を設定できるようになりました。Enterprise管理者は、デフォルトブランチ名についての自分の選択をOrganization群全体に強制することも、個々のOrganizationが独自の選択をできるようにすることもできます。 - 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. + Enterpriseレベルでデフォルトブランチの設定をしてオプトアウトしないかぎり、GHES 3.1では新しく作成されるリポジトリのデフォルトブランチは`main`に設定されます。 {% 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). + この変更は、デフォルトブランチの名前を変更したいプロジェクトやメンテナをサポートするためにGitHubが行っている多くの変更の中の1つです。行われている変更について詳しく学ぶには、[github/名称変更](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. + - 様々な種類のログに対するPIDの追加を含め、いくつかのログファイルのフォーマットが変更されました。これは、GitHub Enterprise Supportが問題のトラブルシューティングのためにサポートバンドルを利用する方法には影響しません。 + - webhookの 設定APIに対するPATCHリクエストは、webhookのシークレットを消去しなくなりました。 deprecations: - - heading: Deprecation of GitHub Enterprise Server 2.19 + heading: 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.' + - '**{% data variables.product.prodname_ghe_server %} 2.19は、2020 年11月12日に非推奨となりました**。これは、この日以降は重大なセキュリティの問題に対してであってもパッチリリースが行われなくなるということです。より優れたパフォーマンス、改善されたセキュリティ、新しい機能のために、[{% data variables.product.prodname_ghe_server %}の最新バージョンへのアップグレード](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/)をできるだけ早く行ってください。' - - heading: Deprecation of Legacy GitHub App Webhook Events + heading: 旧来のGitHub App webhookイベントの非推奨化 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/). + - '{% data variables.product.prodname_ghe_server %} 2.21.0から、2つの旧来のGitHub Appsに関連するwebhookイベントが非推奨となり、{% data variables.product.prodname_ghe_server %} 3.2.0で削除されます。非推奨となったイベントの`integration_installation`と`integration_installation_repositories`には、サポートされることになる同等のイベントがあります。詳細な情報は[非推奨化のアナウンスのblogポスト](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/)にあります。' - - heading: Deprecation of Legacy GitHub Apps Endpoint + heading: 旧来の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/). + - '{% data variables.product.prodname_ghe_server %} 2.21.0から、インストールアクセストークンを作成するための旧来のGitHub Appsのエンドポイントが非推奨となり、{% data variables.product.prodname_ghe_server %} 3.2.0で削除されます。詳細な情報は[非推奨化のアナウンスのblogポスト](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/)にあります。' - - heading: Deprecation of OAuth Application API + heading: OAuth Application APIの非推奨化 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/). + - GitHubは、パスパラメータとして`access_token`を含むOAuthのアプリケーションエンドポイントをサポートしなくなりました。`access_token`をリクエストのボディに移すことにより、OAuth Appsのためのトークンをセキュアに管理できるようにする、新しいエンドポイントが導入されます。非推奨にはなりましたが、これらのエンドポイントはこのバージョンではまだ利用可能です。これらのエンドポイントは、{% data variables.product.prodname_ghe_server %} 3.4で削除しようとしています。詳細については[非推奨化のアナウンスのblogポスト](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/)を参照してください。 - - heading: Deprecation of support for Semiotic + heading: Semioticのサポートの非推奨化 notes: - - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - サービスは、広く使われていなかったPull Requestのビューの"Find by Symbol"体験をサポートしました。 - - heading: Deprecation of workflow commands + heading: ワークフローコマンドの非推奨化 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/).' + - '{% data variables.product.prodname_actions %}の`set-env`及び`add-path`ワークフローコマンドは非推奨になりました。詳しい情報については[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 release candidates in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. - - The image and upgrade package download size has increased. Customers on slow internet connections may find the packages take longer to download. + - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 + - リリース候補1は、クラスタモードをサポートしていません。 + - カスタムのファイアウォールのルールは、アップグレードの際に維持されません。 + - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.blog/2016-02-18-upload-files-to-your-repositories/)が、不正にリポジトリに直接追加されてしまいます。 + - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 + - Actionsのセットアップが成功しなかった場合に、続けてActionsを無効化すると、最初のユーザを作成できず、アプライアンスを利用できません。 + - '"Mandatory message viewed"監査ログイベントが保存されません。' + - 'レプリケーションを開始するために`ghe-repl-setup`を実行できるようになる前に、最初のセットアップの間に`ghe-config-apply`をレプリカで実行しておかなければなりません。' + - Backup-utilsが、不要なメールを管理者に送信することがあります。 + - Organizationのメンバービューページに、正しくないPackagesの設定が表示されます + - Enterpriseのオーナーとして自分自身を削除すると、404ページにリダイレクトされます。処理は成功します。 + - 'Nomadのジョブキューがクリアされるまで、`ghe-config-apply`が`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アップグレードパッケージでアップグレードしてください。 + - イメージとアップグレードパッケージのダウンロードサイズは増加しました。低速なインターネット接続をお使いのお客様は、パッケージのダウンロードに時間がかかることがあります。 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).' + - '{% data variables.product.prodname_ghe_server %} 3.0は、[バックアップとディザスタリカバリ](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance)のために、最低でも[GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils)を必要とします。' diff --git a/translations/ja-JP/data/release-notes/3-0/0-rc2.yml b/translations/ja-JP/data/release-notes/3-0/0-rc2.yml index 0e6ed5fd3f..345c7c7ca9 100644 --- a/translations/ja-JP/data/release-notes/3-0/0-rc2.yml +++ b/translations/ja-JP/data/release-notes/3-0/0-rc2.yml @@ -1,25 +1,25 @@ --- date: '2021-01-29' release_candidate: true -intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +intro: リリース候補バージョンは、非プロダクション環境でテストすべきです。リリース候補プログラムに関する詳しい情報については、[GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) もしくは[新リリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)を参照してください。 sections: bugs: - - heading: Fixes for known issues from Release Candidate 1 + heading: リリース候補1からの既知の問題の修正 notes: - - If you disabled GitHub Actions following an unsuccessful attempt to set up GitHub Actions, then you will not be able to create the first user and use the appliance. - - The "Mandatory message viewed" audit log event was not being saved. - - '`ghe-config-apply` needed to run on a replica during an initial setup before `ghe-repl-setup` could run to start replication.' - - Removing yourself as an enterprise owner returned a 404. + - GitHub Actionsのセットアップに失敗した後に、続けてGitHub Actionsを無効化すると、最初のユーザを作成できず、アプライアンスを使うことができなくなります。 + - '"Mandatory message viewed"監査ログイベントが保存されませんでした。' + - 'レプリケーションを開始するために`ghe-repl-setup`を実行できるようになる前に、初期のセットアップの間に`ghe-config-apply`をレプリカで実行しておかなければなりません。' + - Enterpriseオーナーとして自分を削除すると、404が返されます。 - - heading: Fixes for other issues + heading: 他の問題の修正 notes: - - Issues with migrations and upgrades to 3.0.0 have been fixed. - - Backup Utilities versioning now works for release candidate versions. - - Generating a support bundle resulted in an error in the orchestrator logs. - - A large restore could result in Redis running out of memory. - - The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method. - - GitHub Actions can only be enabled if the required storage is also configured. - - '`ghe-repl-status` could silently fail if MSSQL replication is not configured.' + - 3.0.0への移行とアップグレードの問題が修正されました。 + - Backup Utilitiesのバージョン管理が、リリース候補のバージョンでも動作するようになりました。 + - Support Bundleを生成すると、orchestratorのログにエラーが残りました。 + - 大規模なリストアを行うと、Redisがメモリ不足になることがありました。 + - 管理コンソールのGitHub Actionsを有効化するチェックボックスは、どの認証方式でも表示されるようになりました。 + - GitHub Actionsは、必要なストレージも設定されている場合にのみ有効化できます。 + - 'MSSQLのレプリケーションが設定されていないと、`ghe-repl-status`は何も出力せずに失敗することがあります。' known_issues: - - The known issues for Release Candidate 1 still apply, excluding the bug fixes listed. + - リストされたバグの修正分を除き、リリース候補1の既知の問題は引き続き残っています。 diff --git a/translations/ja-JP/data/reusables/actions/enterprise-beta.md b/translations/ja-JP/data/reusables/actions/enterprise-beta.md index 0a8ab6cecd..0c674122af 100644 --- a/translations/ja-JP/data/reusables/actions/enterprise-beta.md +++ b/translations/ja-JP/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,12 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**注釈:** {% data variables.product.prodname_ghe_server %} 2.22 での {% data variables.product.prodname_actions %} サポートは、限定パブリックベータです。 To review the external storage requirements and request access to the beta, 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)." +**Note:** {% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. The beta has ended. {% data variables.product.prodname_actions %} is now generally available in {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +
+ +- For more information about upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." +- For more information about configuring {% data variables.product.prodname_actions %} after you upgrade, see the [documentation for {% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server). {% endnote %} {% endif %} diff --git a/translations/ja-JP/data/reusables/actions/enterprise-common-prereqs.md b/translations/ja-JP/data/reusables/actions/enterprise-common-prereqs.md index 28640248bb..a8b97bd7d8 100644 --- a/translations/ja-JP/data/reusables/actions/enterprise-common-prereqs.md +++ b/translations/ja-JP/data/reusables/actions/enterprise-common-prereqs.md @@ -1,4 +1,4 @@ -* {% data reusables.actions.enterprise-hardware-considerations %} +* Review the hardware requirements for {% data variables.product.prodname_actions %}. 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#review-hardware-considerations)." * TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." {% note %} diff --git a/translations/ja-JP/data/reusables/actions/enterprise-hardware-considerations.md b/translations/ja-JP/data/reusables/actions/enterprise-hardware-considerations.md index 24c077bbae..98ac65f438 100644 --- a/translations/ja-JP/data/reusables/actions/enterprise-hardware-considerations.md +++ b/translations/ja-JP/data/reusables/actions/enterprise-hardware-considerations.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "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)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. +If you {% if currentVersion == "enterprise-server@2.22" %} configured the beta of{% else %} configure{% endif %} {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, we recommend that you provision additional CPU and memory resources. The additional resources you need to provision depend on the number of workflows your users run concurrently, and the overall levels of activity for your instance. diff --git a/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md index 48f3c5a99a..733e8e8a97 100644 --- a/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md +++ b/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -1,7 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. This option controls access to all {% data variables.product.prodname_advanced_security %} features including {% if currentVersion == "free-pro-team@latest" %}dependency review,{% endif %} {% data variables.product.prodname_code_scanning %}, and {% data variables.product.prodname_secret_scanning %}. {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/code-scanning/enabling-options.md b/translations/ja-JP/data/reusables/code-scanning/enabling-options.md index 3ef6731b26..bbbd1a7893 100644 --- a/translations/ja-JP/data/reusables/code-scanning/enabling-options.md +++ b/translations/ja-JP/data/reusables/code-scanning/enabling-options.md @@ -15,7 +15,7 @@ - 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"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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"). @@ -25,7 +25,7 @@ - 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 %}"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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 %}"). 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 1a1527e5ee..c61e2c2b88 100644 --- a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md @@ -8,7 +8,7 @@ The following table shows, for each package manager: | -------------- | ---------------- | ------------------------- |:--------------------:|:---------:| | Bundler | `bundler` | v1 | | **✓** | | Cargo | `cargo` | v1 | **✓** | | -| Composer | `composer` | v1,v2 | **✓** | | +| Composer | `composer` | v1, v2 | **✓** | | | Docker | `docker` | v1 | **✓** | | | Elixir | `mix` | v1 | **✓** | | | Elm | `elm` | v0.18, v0.19 | **✓** | | @@ -17,7 +17,7 @@ The following table shows, for each package manager: | Go modules | `gomod` | v1 | **✓** | **✓** | | Gradle | `gradle` | see (A) below | **✓** | | | Maven | `maven` | see (B) below | **✓** | | -| npm | `npm` | v6 | **✓** | | +| npm | `npm` | v6, v7 | **✓** | | | NuGet | `nuget` | <= 4.8.
see (C) below | **✓** | | | pip | `pip` | v20 | | | | pipenv | `pip` | <= 2018.11.26 | | | diff --git a/translations/ja-JP/data/reusables/desktop/choose-clone-repository.md b/translations/ja-JP/data/reusables/desktop/choose-clone-repository.md index 2a03327a64..9cbe591688 100644 --- a/translations/ja-JP/data/reusables/desktop/choose-clone-repository.md +++ b/translations/ja-JP/data/reusables/desktop/choose-clone-repository.md @@ -1 +1,13 @@ 1. **File**メニューで、**Clone Repository（リポジトリのクローン）**をクリックしてください。 + + {% mac %} + + ![Mac アプリケーション内の [Clone] メニューオプション](/assets/images/help/desktop/clone-file-menu-mac.png) + + {% endmac %} + + {% windows %} + + ![Windows アプリケーション内の [Clone] メニューオプション](/assets/images/help/desktop/clone-file-menu-windows.png) + + {% endwindows %} diff --git a/translations/ja-JP/data/reusables/desktop/choose-local-path.md b/translations/ja-JP/data/reusables/desktop/choose-local-path.md new file mode 100644 index 0000000000..ce28b76c4d --- /dev/null +++ b/translations/ja-JP/data/reusables/desktop/choose-local-path.md @@ -0,0 +1,13 @@ +1. Click **Choose...** and navigate to a local path where you want to clone the repository. + + {% mac %} + + ![Chooseボタン](/assets/images/help/desktop/clone-choose-button-mac.png) + + {% endmac %} + + {% windows %} + + ![Chooseボタン](/assets/images/help/desktop/clone-choose-button-win.png) + + {% endwindows %} diff --git a/translations/ja-JP/data/reusables/desktop/click-clone.md b/translations/ja-JP/data/reusables/desktop/click-clone.md new file mode 100644 index 0000000000..9ae5d017dd --- /dev/null +++ b/translations/ja-JP/data/reusables/desktop/click-clone.md @@ -0,0 +1,14 @@ +1. **Clone**をクリックします。 + + {% mac %} + + ![Cloneボタン](/assets/images/help/desktop/clone-button-mac.png) + + {% endmac %} + + {% windows %} + + ![Cloneボタン](/assets/images/help/desktop/clone-button-win.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/desktop/cloning-location-tab.md b/translations/ja-JP/data/reusables/desktop/cloning-location-tab.md index 2b1c2fad78..7d9d418a6e 100644 --- a/translations/ja-JP/data/reusables/desktop/cloning-location-tab.md +++ b/translations/ja-JP/data/reusables/desktop/cloning-location-tab.md @@ -1 +1,13 @@ 1. クローンしたいリポジトリの場所に対応するタブをクリックしてください。 **URL**をクリックし、リポジトリの場所を入力することもできます。 + + {% mac %} + + ![[Clone a repository] メニュー内の [Location] タブ](/assets/images/help/desktop/choose-repository-location-mac.png) + + {% endmac %} + + {% windows %} + + ![[Clone a repository] メニュー内の [Location] タブ](/assets/images/help/desktop/choose-repository-location-win.png) + + {% endwindows %} diff --git a/translations/ja-JP/data/reusables/desktop/cloning-repository-list.md b/translations/ja-JP/data/reusables/desktop/cloning-repository-list.md index dec00a0566..5b5ef1962f 100644 --- a/translations/ja-JP/data/reusables/desktop/cloning-repository-list.md +++ b/translations/ja-JP/data/reusables/desktop/cloning-repository-list.md @@ -1 +1,14 @@ 1. クローンしたいリポジトリをリストから選択します。 + + + {% mac %} + + ![リポジトリリストのクローン](/assets/images/help/desktop/clone-a-repository-list-mac.png) + + {% endmac %} + + {% windows %} + + ![リポジトリリストのクローン](/assets/images/help/desktop/clone-a-repository-list-win.png) + + {% endwindows %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/desktop/fork-type-prompt.md b/translations/ja-JP/data/reusables/desktop/fork-type-prompt.md new file mode 100644 index 0000000000..1067dab748 --- /dev/null +++ b/translations/ja-JP/data/reusables/desktop/fork-type-prompt.md @@ -0,0 +1,42 @@ +1. If you plan to use this fork for contributing to the original upstream repository, click **To contribute to the parent project**. + + {% mac %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/mac-fork-options-prompt.png) + + {% endmac %} + + {% windows %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/windows-fork-options-prompt.png) + + {% endwindows %} + +2. If you plan to use this fork for a project not connected to the upstream, click **For my own purposes**. + + {% mac %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/mac-fork-own-purposes.png) + + {% endmac %} + + {% windows %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/windows-fork-own-purposes.png) + + {% endwindows %} + +3. Click **Continue**. + + {% mac %} + + ![The continue button](/assets/images/help/desktop/mac-forking-continue.png) + + {% endmac %} + + {% windows %} + + ![The continue button](/assets/images/help/desktop/windows-forking-continue.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/desktop/open-repository-settings.md b/translations/ja-JP/data/reusables/desktop/open-repository-settings.md new file mode 100644 index 0000000000..5e298edc85 --- /dev/null +++ b/translations/ja-JP/data/reusables/desktop/open-repository-settings.md @@ -0,0 +1,14 @@ +1. Open the **Repository** menu, then click **Repository settings...**. + + {% mac %} + + ![Repository settings menu option in the Mac app](/assets/images/help/desktop/mac-repository-settings.png) + + {% endmac %} + + {% windows %} + + ![Repository settings menu option in the Windows app](/assets/images/help/desktop/windows-repository-settings.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/desktop/select-fork-behavior.md b/translations/ja-JP/data/reusables/desktop/select-fork-behavior.md new file mode 100644 index 0000000000..9672212ec2 --- /dev/null +++ b/translations/ja-JP/data/reusables/desktop/select-fork-behavior.md @@ -0,0 +1,28 @@ +1. Click **Fork behavior**, then select how you want to use the fork. + + {% mac %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-menu-contribute.png) + + {% endmac %} + + {% windows %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-menu-contribute.png) + + {% endwindows %} + +2. [**Save**] をクリックします。 + + {% mac %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-save.png) + + {% endmac %} + + {% windows %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-save.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/education/apply-for-team.md b/translations/ja-JP/data/reusables/education/apply-for-team.md index f8f9508edf..00243b1c32 100644 --- a/translations/ja-JP/data/reusables/education/apply-for-team.md +++ b/translations/ja-JP/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- 無料の[{% data variables.product.prodname_team %}](/articles/github-s-products)に応募してください。{% data variables.product.prodname_team %}では、無制限のユーザとプライベートリポジトリが利用できます。 For more information, see "[Apply for an educator or researcher discount](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)." +- 無料の[{% data variables.product.prodname_team %}](/articles/github-s-products)に応募してください。{% data variables.product.prodname_team %}では、無制限のユーザとプライベートリポジトリが利用できます。 詳しい情報については、 「[教育者割引または研究者割引への応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md b/translations/ja-JP/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md new file mode 100644 index 0000000000..63fa9473e7 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md @@ -0,0 +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 including with your account. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md index b3d2f79f51..e860480c16 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md @@ -1 +1,2 @@ -1. "{% octicon "gear" aria-label="The Settings gear" %} Setteings（設定）"の下で、**Hooks（フック）**をクリックしてください。 ![Enterpriseアカウント設定サイドバー内のフックタブ](/assets/images/help/business-accounts/settings-hooks-tab.png) +1. Under "{% octicon "gear" aria-label="The Settings gear" %} Settings", click **Hooks**. + ![Hooks tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-hooks-tab.png) diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md index 919a20f356..af9df45fdd 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md @@ -1 +1,2 @@ -1. "{% octicon "gear" aria-label="The Settings gear" %} Setteings（設定）"の下で、**Messages（メッセージ）**をクリックしてください。 ![Enterprise設定サイドバー内のメッセージタブ](/assets/images/enterprise/business-accounts/settings-messages-tab.png) +1. Under **{% octicon "gear" aria-label="The Settings gear" %} Settings**, click **Messages**. + ![Messages tab in the enterprise settings sidebar](/assets/images/enterprise/business-accounts/settings-messages-tab.png) diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/payment-information-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/payment-information-tab.md new file mode 100644 index 0000000000..4de0966ad7 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/payment-information-tab.md @@ -0,0 +1 @@ +1. Under "Billing", click **Payment information**. diff --git a/translations/ja-JP/data/reusables/enterprise_installation/about-adjusting-resources.md b/translations/ja-JP/data/reusables/enterprise_installation/about-adjusting-resources.md new file mode 100644 index 0000000000..2d6c2fe4e6 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_installation/about-adjusting-resources.md @@ -0,0 +1 @@ +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)." diff --git a/translations/ja-JP/data/reusables/enterprise_installation/aws-supported-instance-types.md b/translations/ja-JP/data/reusables/enterprise_installation/aws-supported-instance-types.md index 264172e0c2..c6a243b537 100644 --- a/translations/ja-JP/data/reusables/enterprise_installation/aws-supported-instance-types.md +++ b/translations/ja-JP/data/reusables/enterprise_installation/aws-supported-instance-types.md @@ -1,37 +1,13 @@ -{% data variables.product.prodname_ghe_server %} は、次の EC2インスタンスタイプでサポートされています。 詳しい情報については[AWS EC2インスタンスタイプの概要ページ](http://aws.amazon.com/ec2/instance-types/)を参照してください。 +{% data variables.product.prodname_ghe_server %} is supported on the following EC2 instance sizes. 詳しい情報については[AWS EC2インスタンスタイプの概要ページ](http://aws.amazon.com/ec2/instance-types/)を参照してください。 -| EC2インスタンスタイプ | モデル | -| ------------ | ---------------------------------- | -| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | - -| EC2インスタンスタイプ | モデル | -| ------------ | ---------------------------------- | -| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | - -| EC2インスタンスタイプ | モデル | -| ------------ | -------------------------------------------------------------------- | -| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | - -| EC2インスタンスタイプ | モデル | -| ------------ | --------------------- | -| M3 | m3.xlarge, m3.2xlarge | - -| EC2インスタンスタイプ | モデル | -| ------------ | ----------------------------------------------------------- | -| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | - -| EC2インスタンスタイプ | モデル | -| ------------ | --------------------------------------------------------------------- | -| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | - -| EC2インスタンスタイプ | モデル | -| ------------ | -------------------------------------------------------------------- | -| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | - -| EC2インスタンスタイプ | モデル | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} - -| EC2インスタンスタイプ | モデル | -| ------------ | ------------------------ | -| X1 | x1.16xlarge, x1.32xlarge | +| 種類 | Size | +|:-- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | +| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | +| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | +| M3 | m3.xlarge, m3.2xlarge | +| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | +| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | +| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | +| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} +| X1 | x1.16xlarge, x1.32xlarge | diff --git a/translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index d3dc011120..271ee1b299 100644 --- a/translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,6 +1,5 @@ - [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} -- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} -- [Optional features](#optional-features){% endif %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %} - [ストレージ](#storage) - [CPU and memory](#cpu-and-memory) @@ -8,20 +7,7 @@ We recommend different hardware configurations depending on the number of user licenses for {% data variables.product.product_location %}. If you provision more resources than the minimum requirements, your instance will perform and scale better. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - -- You must configure at least one runner for {% data variables.product.prodname_actions %} workflows. 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」を参照してください。 -- You must configure external blob storage. 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)." -- You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} 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 | Additional vCPUs | Additional memory | - |:----------------------- | ----------------:| -----------------:| - | Light testing | 4 | 30.5 GB | - | 25 | 8 | 61 GB | - | 35 | 16 | 122 GB | - | 100 | 32 | 244 GB | - -{% endif %} +{% data reusables.enterprise_installation.hardware-rec-table %} #### ストレージ @@ -31,7 +17,7 @@ Your instance requires a persistent data disk separate from the root disk. 詳 {% if currentVersion ver_gt "enterprise-server@2.21" %} -If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. 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)." +To configure{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you must provide external blob storage. 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)." {% endif %} @@ -39,7 +25,7 @@ You can resize your instance's root disk by building a new instance or using an #### 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. +The CPU and memory resources that {% data variables.product.prodname_ghe_server %} requires depend on the levels of activity for users, automations, and integrations. {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data reusables.actions.enterprise-hardware-considerations %}{% endif %} {% data reusables.enterprise_installation.increasing-cpus-req %} @@ -49,4 +35,4 @@ You can resize your instance's root disk by building a new instance or using an {% endwarning %} -You can increase your instance's CPU or memory resources. For more information, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." +You can increase your instance's CPU or memory resources. 詳しい情報については、「[CPU またはメモリリソースを増やす](/enterprise/admin/installation/increasing-cpu-or-memory-resources)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/ja-JP/data/reusables/enterprise_installation/hardware-rec-table.md index c621d139a7..b47a8eb318 100644 --- a/translations/ja-JP/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/ja-JP/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,20 +1,20 @@ -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." +**Note**: If you joined the beta for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} and enabled the features, your instance requires additional hardware resources. 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)." {% endnote %} {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -| ユーザライセンス | vCPUs | メモリ | アタッチされたストレージ | ルートストレージ | -|:---------------------- | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| --------:| -| トライアル、デモ、あるいは10人の軽量ユーザ | 2
or [**4**](#optional-features) | 16 GB
or [**32 GB**](#optional-features) | 100 GB
or [**150 GB**](#optional-features) | 200 GB | -| 10-3000 | 4
or [**8**](#optional-features) | 32 GB
or [**48 GB**](#optional-features) | 250 GB
or [**300 GB**](#optional-features) | 200 GB | -| 3000-5000 | 8
or [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | -| 5000-8000 | 12
or [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | -| 8000-10000+ | 16
or [**20**](#optional-features) | 128 GB
or [**160 GB**](#optional-features) | 1000 GB | 200 GB | +| ユーザライセンス | vCPUs | メモリ | アタッチされたストレージ | ルートストレージ | +|:---------------------- | -----:| ------:| ------------:| --------:| +| トライアル、デモ、あるいは10人の軽量ユーザ | 4 | 32 GB | 150 GB | 200 GB | +| 10-3000 | 8 | 48 GB | 300 GB | 200 GB | +| 3000-5000 | 12 | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 16 | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 20 | 160 GB | 1000 GB | 200 GB | {% else %} @@ -28,22 +28,20 @@ {% endif %} -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)." +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +If you plan to configure {% data variables.product.prodname_actions %} for your instance, you should provision additional resources. You must also configure at least one self-hosted runner to execute workflows. 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)." + +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} #### Beta features in {% data variables.product.prodname_ghe_server %} 2.22 -You can sign up for beta features available in {% data variables.product.prodname_ghe_server %} 2.22 such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [release notes for the 2.22 series](https://enterprise.github.com/releases/series/2.22#release-2.22.0) on the {% data variables.product.prodname_enterprise %} website. +{% data variables.product.prodname_ghe_server %} 2.22 offered features in beta, such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [{% data variables.product.prodname_ghe_server %} 2.22 release notes](/enterprise-server@2.22/admin/release-notes#2.22.0). -If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". - -{% elsif currentVersion ver_gt "enterprise-server@2.22" %} - -#### Optional features - -You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. 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)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." - -If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +If you enabled beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". {% endif %} diff --git a/translations/ja-JP/data/reusables/gated-features/auto-merge.md b/translations/ja-JP/data/reusables/gated-features/auto-merge.md index 72a58ba07d..acfb4dddff 100644 --- a/translations/ja-JP/data/reusables/gated-features/auto-merge.md +++ b/translations/ja-JP/data/reusables/gated-features/auto-merge.md @@ -1 +1 @@ -Auto-merge for pull requests 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" %}{% data reusables.gated-features.more-info %}{% endif %} \ No newline at end of file +Auto-merge for pull requests 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 %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} 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 69e6abf27f..35598cce54 100644 --- a/translations/ja-JP/data/reusables/gated-features/code-scanning.md +++ b/translations/ja-JP/data/reusables/gated-features/code-scanning.md @@ -1 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled. +{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository. +{%- else %} +{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} 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 38516f39fc..c474c4fad9 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 @@ -1,8 +1,8 @@ -| 仮想環境 | YAMLのワークフローラベル | -| -------------------- | ---------------------------------- | -| Windows Server 2019 | `windows-latest` or `windows-2019` | -| Ubuntu 20.04 | `ubuntu-20.04` | -| Ubuntu 18.04 | `ubuntu-latest`または`ubuntu-18.04` | -| Ubuntu 16.04 | `ubuntu-16.04` | -| macOS Big Sur 11.0 | `macos-11.0` | -| macOS Catalina 10.15 | `macos-latest`もしくは`macos-10.15` | +| 仮想環境 | YAMLのワークフローラベル | +| -------------------- | -------------------------------------------- | +| Windows Server 2019 | `windows-latest` or `windows-2019` | +| Ubuntu 20.04 | `ubuntu-latest` (see note) or `ubuntu-20.04` | +| Ubuntu 18.04 | `ubuntu-latest` (see note) or `ubuntu-18.04` | +| Ubuntu 16.04 | `ubuntu-16.04` | +| macOS Big Sur 11.0 | `macos-11.0` | +| macOS Catalina 10.15 | `macos-latest`もしくは`macos-10.15` | diff --git a/translations/ja-JP/data/reusables/github-actions/ubuntu-runner-preview.md b/translations/ja-JP/data/reusables/github-actions/ubuntu-runner-preview.md index 61d85514ce..6eb91edc13 100644 --- a/translations/ja-JP/data/reusables/github-actions/ubuntu-runner-preview.md +++ b/translations/ja-JP/data/reusables/github-actions/ubuntu-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**ノート:** Ubuntu 20.04仮想環境は、現在プレビューでのみ提供されています。 YAMLワークフローラベルの`ubuntu-latest`は、引き続きUbuntu 18.04仮想環境を利用します。 +**Note:** The `ubuntu-latest` label is currently being migrated from the Ubuntu 18.04 virtual environment to Ubuntu 20.04. Specifying the `ubuntu-latest` label during the migration might use either virtual environment. To explicitly use Ubuntu 20.04 or Ubuntu 18.04, specify `ubuntu-20.04` or `ubuntu-18.04`. When the migration is complete, `ubuntu-latest` will use the Ubuntu 20.04 virtual environment. For more information about the migration, see "[Ubuntu-latest workflows will use Ubuntu-20.04](https://github.com/actions/virtual-environments/issues/1816)." {% endnote %} diff --git a/translations/ja-JP/data/reusables/github-insights/events-tab.md b/translations/ja-JP/data/reusables/github-insights/events-tab.md index 1e965ce430..e17ffdc31b 100644 --- a/translations/ja-JP/data/reusables/github-insights/events-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/events-tab.md @@ -1 +1,2 @@ -1. **{% octicon "gear" aria-label="The gear icon" %} Settings（設定）**の下で**Events（イベント）**をクリックしてください。 ![イベントタブ](/assets/images/help/insights/events-tab.png) +1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Events**. + ![Events tab](/assets/images/help/insights/events-tab.png) diff --git a/translations/ja-JP/data/reusables/github-insights/exclude-files-tab.md b/translations/ja-JP/data/reusables/github-insights/exclude-files-tab.md index f80ca371e6..32d4cbb997 100644 --- a/translations/ja-JP/data/reusables/github-insights/exclude-files-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/exclude-files-tab.md @@ -1 +1,2 @@ -1. **{% octicon "gear" aria-label="The gear icon" %} Settings（設定）**の下で**Exclude files（ファイルの除外）**をクリックしてください。 ![ファイルの除外タブ](/assets/images/help/insights/exclude-files-tab.png) +1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Exclude files**. + ![Exclude files tab](/assets/images/help/insights/exclude-files-tab.png) diff --git a/translations/ja-JP/data/reusables/github-insights/repo-groups-tab.md b/translations/ja-JP/data/reusables/github-insights/repo-groups-tab.md index 20b00c1896..f4670fb260 100644 --- a/translations/ja-JP/data/reusables/github-insights/repo-groups-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/repo-groups-tab.md @@ -1 +1,2 @@ -1. **{% octicon "gear" aria-label="The gear icon" %} Settings（設定）**の下で**Repo groups（リポジトリグループ）**をクリックしてください。 ![リポジトリグループタブ](/assets/images/help/insights/repo-groups-tab.png) +1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Repo groups**. + ![Repo groups tab](/assets/images/help/insights/repo-groups-tab.png) diff --git a/translations/ja-JP/data/reusables/github-insights/repositories-tab.md b/translations/ja-JP/data/reusables/github-insights/repositories-tab.md index cdfa276583..6dae008abb 100644 --- a/translations/ja-JP/data/reusables/github-insights/repositories-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/repositories-tab.md @@ -1 +1,2 @@ -1. **{% octicon "gear" aria-label="The gear icon" %} Settings（設定）**の下で**Repositories（リポジトリ）**をクリックしてください。 ![[Repositories] タブ](/assets/images/help/insights/repositories-tab.png) +1. Under "**{% octicon "gear" aria-label="The gear icon" %} Settings**", click **Repositories**. + ![Repositories tab](/assets/images/help/insights/repositories-tab.png) diff --git a/translations/ja-JP/data/reusables/github-insights/settings-tab.md b/translations/ja-JP/data/reusables/github-insights/settings-tab.md index 7595a08a32..3dc57e9b30 100644 --- a/translations/ja-JP/data/reusables/github-insights/settings-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/settings-tab.md @@ -1 +1,2 @@ -1. {% data variables.product.prodname_insights %}で、**{% octicon "gear" aria-label="The gear icon" %} Settings（の設定）**をクリックしてください。 ![設定タブ](/assets/images/help/insights/settings-tab.png) +1. In {% data variables.product.prodname_insights %}, click **{% octicon "gear" aria-label="The gear icon" %} Settings**. + ![Settings tab](/assets/images/help/insights/settings-tab.png) diff --git a/translations/ja-JP/data/reusables/github-insights/teams-tab.md b/translations/ja-JP/data/reusables/github-insights/teams-tab.md index 1bfc73e8cf..545533de53 100644 --- a/translations/ja-JP/data/reusables/github-insights/teams-tab.md +++ b/translations/ja-JP/data/reusables/github-insights/teams-tab.md @@ -1 +1,2 @@ -1. **{% octicon "gear" aria-label="The gear icon" %} Settings（設定）**の下で**Teams**をクリックしてください。 ![Teamsタブ](/assets/images/help/insights/teams-tab.png) +1. Under **{% octicon "gear" aria-label="The gear icon" %} Settings**, click **Teams**. + ![Teams tab](/assets/images/help/insights/teams-tab.png) diff --git a/translations/ja-JP/data/reusables/organizations/organizations_include.md b/translations/ja-JP/data/reusables/organizations/organizations_include.md index b18e7f5842..ec7d4cb66e 100644 --- a/translations/ja-JP/data/reusables/organizations/organizations_include.md +++ b/translations/ja-JP/data/reusables/organizations/organizations_include.md @@ -6,3 +6,4 @@ Organizationには以下が含まれます。 - [Nested teams that reflect your company or group's structure](/articles/about-teams) with cascading access permissions and mentions{% if currentVersion != "github-ae@latest" %} - Organizationのオーナーがメンバーの[２要素認証（2FA）のステータス](/articles/about-two-factor-authentication)を見る機能。 - The option to [require all organization members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} +{% if currentVersion == "free-pro-team@latest" %}- The option to purchase a license for {% data variables.product.prodname_GH_advanced_security %} and use the features on private repositories. {% data reusables.advanced-security.more-info-ghas %}{% endif %} diff --git a/translations/ja-JP/data/reusables/pages/new-or-existing-repo.md b/translations/ja-JP/data/reusables/pages/new-or-existing-repo.md index d88d41c67b..28082cc8a4 100644 --- a/translations/ja-JP/data/reusables/pages/new-or-existing-repo.md +++ b/translations/ja-JP/data/reusables/pages/new-or-existing-repo.md @@ -1,3 +1,5 @@ サイトが独立プロジェクトなら、サイトのソースコードを保存するために新しいリポジトリを作成できます。 If your site is associated with an existing project, you can add the source code {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}to that project's repository, in a `/docs` folder on the default branch or on a different branch.{% else %}for your site to a `gh-pages` branch or a `docs` folder on the `master` branch in that project's repository.{% endif %} For example, if you're creating a site to publish documentation for a project that's already on {% data variables.product.product_name %}, you may want to store the source code for the site in the same repository as the project. +{% if currentVersion == "free-pro-team@latest" %}If the account that owns the repository uses {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_free_team %}, the repository must be public.{% endif %} + 既存のリポジトリにサイトを作成したいのなら、[サイトの作成](#creating-your-site)セクションまでスキップしてください。 diff --git a/translations/ja-JP/data/reusables/pull_requests/you-can-auto-merge.md b/translations/ja-JP/data/reusables/pull_requests/you-can-auto-merge.md index 410aec2a8e..5da386a3d1 100644 --- a/translations/ja-JP/data/reusables/pull_requests/you-can-auto-merge.md +++ b/translations/ja-JP/data/reusables/pull_requests/you-can-auto-merge.md @@ -1,3 +1,3 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} You can configure a pull request to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md index e67eeed7c6..ea2eaeccfb 100644 --- a/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| キー | 種類 | 説明 | -| -------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | +| キー | 種類 | 説明 | +| -------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | diff --git a/translations/ja-JP/data/variables/action_code_examples.yml b/translations/ja-JP/data/variables/action_code_examples.yml index 6d27178d24..b648ccc73e 100644 --- a/translations/ja-JP/data/variables/action_code_examples.yml +++ b/translations/ja-JP/data/variables/action_code_examples.yml @@ -24,7 +24,7 @@ - labels - title: Add releases to GitHub - description: Publish Github releases in an action + description: Publish GitHub releases in an action languages: 'Dockerfile, Shell' href: elgohr/Github-Release-Action tags: @@ -32,7 +32,7 @@ - publishing - title: Publish a docker image to Dockerhub - description: A Github Action used to build and publish Docker images + description: A GitHub Action used to build and publish Docker images languages: 'Dockerfile, Shell' href: elgohr/Publish-Docker-Github-Action tags: @@ -123,7 +123,7 @@ - publishing - title: Label your Pull Requests auto-magically (using committed files) - description: Github action to label your pull requests auto-magically (using committed files) + description: GitHub action to label your pull requests auto-magically (using committed files) languages: 'TypeScript, Dockerfile, JavaScript' href: Decathlon/pull-request-labeler-action tags: @@ -132,7 +132,7 @@ - labels - title: Add Label to your Pull Requests based on the author team name - description: Github action to label your pull requests based on the author name + description: GitHub action to label your pull requests based on the author name languages: 'TypeScript, JavaScript' href: JulienKode/team-labeler-action tags: diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml index cdfd06514e..2b48821c83 100644 --- a/translations/ja-JP/data/variables/product.yml +++ b/translations/ja-JP/data/variables/product.yml @@ -147,10 +147,10 @@ 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://docs.github.com/rest{% elsif enterpriseServerVersions contains currentVersion %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif currentVersion == "github-ae@latest" %}https://docs.github.com/github-ae@latest/rest{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% endif %} #Use this inside command-line code blocks #Enterprise OAuth paths that don't include "/graphql" or "/api/v3" oauth_host_code: >- @@ -159,10 +159,10 @@ device_authorization_url: >- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}[`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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/graphql{% endif %} 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 8110e5d167..251556fb90 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 @@ -7,7 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: '개요' +type: overview --- {% data reusables.actions.enterprise-beta %} @@ -63,7 +63,7 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe {% data reusables.github-actions.usage-api-requests %} - **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %} -### Supported operating systems for self-hosted runners +### Supported architectures and operating systems for self-hosted runners The following operating systems are supported for the self-hosted runner application. @@ -92,6 +92,14 @@ The following operating systems are supported for the self-hosted runner applica - macOS 10.13 (High Sierra) or later +#### Architectures + +The following processor architectures are supported for the self-hosted runner application. + +- `x64` - Linux, macOS, Windows. +- `ARM64` - Linux only. +- `ARM32` - Linux only. + {% if enterpriseServerVersions contains currentVersion %} ### Supported actions on self-hosted runners 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 77537c94ae..49ccca3a22 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 @@ -29,7 +29,7 @@ A self-hosted runner automatically receives certain labels when it is added to { * `self-hosted`: Default label applied to all self-hosted runners. * `linux`, `windows`, or `macOS`: Applied depending on operating system. -* `x86`, `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. +* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. You can use your workflow's YAML to send jobs to a combination of these labels. In this example, a self-hosted runner that matches all three labels will be eligible to run the job: diff --git a/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md index 912148bcae..2ebc265405 100644 --- a/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md @@ -41,12 +41,17 @@ Windows virtual machines are configured to run as administrators with User Accou ### Supported runners and hardware resources -Each virtual machine has the same hardware resources available. +Hardware specification for Windows and Linux virtual machines: - 2-core CPU - 7 GB of RAM memory - 14 GB of SSD disk space +Hardware specification for macOS virtual machines: +- 3-core CPU +- 14 GB of RAM memory +- 14 GB of SSD disk space + {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} @@ -71,9 +76,13 @@ The software tools included in {% data variables.product.prodname_dotcom %}-host {% data variables.product.prodname_dotcom %}-hosted runners include the operating system's default built-in tools, in addition to the packages listed in the above references. For example, Ubuntu and macOS runners include `grep`, `find`, and `which`, among other default tools. -Workflow logs include a link to the preinstalled tools on the runner. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." +Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will tell you the the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -If there is a tool that you'd like to request, please open an issue at [actions/virtual-environments](https://github.com/actions/virtual-environments). +We recommend using actions to interact with the software installed on runners. This approach has several benefits: +- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters +- It ensures the tool versions used in your workflow will remain the same regardless of software updates + +If there is a tool that you'd like to request, please open an issue at [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners. ### IP addresses diff --git a/translations/ko-KR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/ko-KR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index 08a27ed2a3..185e01118d 100644 --- a/translations/ko-KR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/ko-KR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -73,7 +73,7 @@ If the server on which you are running {% endif %} #### Enabling code scanning for individual repositories -After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. 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)." +After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." ### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %} If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. diff --git a/translations/ko-KR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/ko-KR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index f8f398f3f1..cbe865be86 100644 --- a/translations/ko-KR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md +++ b/translations/ko-KR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md @@ -20,7 +20,7 @@ For encryption in transit, {% data variables.product.product_name %} uses Transp The key that you provide is stored in a hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages. -To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and delete your encryption key. Note that deleting your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation. +To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation. ### Adding or updating an encryption key @@ -48,24 +48,24 @@ Your 2048 bit RSA private key should be in PEM format, for example in a file cal curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` -### Deleting your encryption key +### Disabling your encryption key -To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by deleting your encryption key. +To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled. -To unfreeze your enterprise after you've deleted your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)." - -1. To delete your key and disable encryption at rest, use the `DELETE /enterprise/encryption` endpoint. +1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently. ```shell curl -X DELETE http(s)://hostname/api/v3/enterprise/encryption ``` -2. Optionally, check the status of the delete operation. +2. Optionally, check the status of the delete operation. It takes approximately ten minutes to disable encryption at rest. ```shell curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` +To unfreeze your enterprise after you've disabled your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)." + ### 더 읽을거리 - "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation diff --git a/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md index 2da8d02184..800a5acd59 100644 --- a/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/ko-KR/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -29,6 +29,26 @@ versions: {% endnote %} +{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %} + +### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later + +Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table. + +| User licenses | vCPUs | Memory | Attached storage | Root storage | +|:------------------------------ | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:| +| Trial, demo, or 10 light users | **4**
_Up from 2_ | **32 GB**
_Up from 16 GB_ | **150 GB**
_Up from 100 GB_ | 200 GB | +| 10 to 3,000 | **8**
_Up from 4_ | **48 GB**
_Up from 32 GB_ | **300 GB**
_Up from 250 GB_ | 200 GB | +| 3,000 to 5000 | **12**
_Up from 8_ | 64 GB | 500 GB | 200 GB | +| 5,000 to 8000 | **16**
_Up from 12_ | 96 GB | 750 GB | 200 GB | +| 8,000 to 10,000+ | **20**
_Up from 16_ | **160 GB**
_Up from 128 GB_ | 1000 GB | 200 GB | + +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% endif %} + ### Taking a snapshot A snapshot is a checkpoint of a virtual machine (VM) at a point in time. We highly recommend taking a snapshot before upgrading your virtual machine so that if an upgrade fails, you can revert your VM back to the snapshot. If you're upgrading to a new feature release, you must take a VM snapshot. If you're upgrading to a patch release, you can attach the existing data disk. diff --git a/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md index 5d3815c6e1..8e42460670 100644 --- a/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/ko-KR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -9,13 +9,7 @@ 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-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} @@ -23,11 +17,33 @@ versions: This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies. +{% endif %} + ### Review hardware considerations +{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %} + +{% note %} + +**Note**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." + +{% endnote %} + +{% endif %} + {% data reusables.actions.enterprise-hardware-considerations %} -{% endif %} +For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform. + +- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) +- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) +- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) +- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) +- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) +- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations) +- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations) + +{% data reusables.enterprise_installation.about-adjusting-resources %} ### External storage requirements @@ -55,7 +71,7 @@ To enable {% data variables.product.prodname_actions %} on {% data variables.pro ### Enabling {% data variables.product.prodname_actions %} -{% 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/). +{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." ### 더 읽을거리 diff --git a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md index 60a7dc7a2e..cc1193853c 100644 --- a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md +++ b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md @@ -8,40 +8,40 @@ versions: free-pro-team: '*' --- -### Cloning repositories -Repositories on {% data variables.product.prodname_dotcom %} exist as remote repositories. You can clone public repositories owned by other people. You can clone your own repository to create a local copy on your computer and sync between the two locations. +### About local repositories +Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer. + +You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. For more information, see "[Syncing your branch](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)." + +When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. For more information, see "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)." + +When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)". You can also clone a repository directly from {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)". -{% mac %} +### Cloning a repository {% data reusables.desktop.choose-clone-repository %} - ![Clone menu option in the Mac app](/assets/images/help/desktop/clone-file-menu-mac.png) {% data reusables.desktop.cloning-location-tab %} - ![Location tabs in the Clone a repository menu](/assets/images/help/desktop/choose-repository-location-mac.png) {% data reusables.desktop.cloning-repository-list %} - ![Clone a repository list](/assets/images/help/desktop/clone-a-repository-list-mac.png) -4. Click **Choose...** and, using the Finder window, navigate to a local path where you want to clone the repository. ![The choose button](/assets/images/help/desktop/clone-choose-button-mac.png) -5. Click **Clone**. ![The clone button](/assets/images/help/desktop/clone-button-mac.png) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} -{% endmac %} - -{% windows %} +### Forking a repository +If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork. {% data reusables.desktop.choose-clone-repository %} - ![Clone menu option in the Windows app](/assets/images/help/desktop/clone-file-menu-windows.png) {% data reusables.desktop.cloning-location-tab %} - ![Location tabs in the Clone a repository menu](/assets/images/help/desktop/choose-repository-location-win.png) {% data reusables.desktop.cloning-repository-list %} - ![Clone a repository list](/assets/images/help/desktop/clone-a-repository-list-win.png) -4. Click **Choose...** and, using Windows Explorer, navigate to a local path where you want to clone the repository. ![The choose button](/assets/images/help/desktop/clone-choose-button-win.png) -5. Click **Clone**. ![The clone button](/assets/images/help/desktop/clone-button-win.png) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} +{% data reusables.desktop.fork-type-prompt %} -{% endwindows %} +### Managing fork behavior +You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}. -### Forking repositories -To contribute to a project where you don't have write access, you can use {% data variables.product.prodname_desktop %} to create a fork of the repository. Changes on your fork don't affect the original repository. You can commit changes on your fork, then open a pull request to the original repository with your proposed changes. For more information, see "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)." +{% data reusables.desktop.open-repository-settings %} +{% data reusables.desktop.select-fork-behavior %} -1. If you've cloned a repository where you don't have write access and try to commit changes, {% data variables.product.prodname_desktop %} will warn that "You don't have write access to **REPOSITORY**. Click **create a fork**. ![Create a fork link](/assets/images/help/desktop/create-a-fork.png) -3. Click **Fork this repository**. ![Fork this repo button](/assets/images/help/desktop/fork-this-repo-button.png) -4. To view your fork on {% data variables.product.prodname_dotcom %}, in the top right corner of {% data variables.product.prodname_dotcom %}, click your profile picture, then click **Your repositories**. ![Your repositories link](/assets/images/help/profile/your-repositories.png) +### 더 읽을거리 +- [About remote repositories](/github/using-git/about-remote-repositories) diff --git a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 6e8a51401d..5136aaff13 100644 --- a/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/ko-KR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -9,7 +9,7 @@ versions: ### About tags in {% data variables.product.prodname_desktop %} -{% data variables.product.prodname_desktop %} allows you to create annotated tags. You can use a tag to mark an individual point in your repository's history, including a version number for a release. For more information about release tags, see "[About releases](/github/administering-a-repository/about-releases)." +{% data variables.product.prodname_desktop %} allows you to create annotated tags. Tags are associated with commits, so you can use a tag to mark an individual point in your repository's history, including a version number for a release. For more information about release tags, see "[About releases](/github/administering-a-repository/about-releases)." {% data reusables.desktop.tags-push-with-commits %} @@ -44,3 +44,7 @@ versions: {% data reusables.desktop.history-tab %} {% data reusables.desktop.delete-tag %} + +### 더 읽을거리 + +- "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation diff --git a/translations/ko-KR/content/developers/apps/activating-beta-features-for-apps.md b/translations/ko-KR/content/developers/apps/activating-beta-features-for-apps.md index f349501d5f..25c83f6d3f 100644 --- a/translations/ko-KR/content/developers/apps/activating-beta-features-for-apps.md +++ b/translations/ko-KR/content/developers/apps/activating-beta-features-for-apps.md @@ -3,6 +3,8 @@ title: Activating beta features for apps intro: 'You can test new app features released in public beta for your {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s.' versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% warning %} diff --git a/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md b/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md index 8305fed871..05a771d379 100644 --- a/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md @@ -110,7 +110,7 @@ The example above uses the maximum expiration time of 10 minutes, after which th ```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" + "documentation_url": "{% data variables.product.doc_url_pre %}" } ``` diff --git a/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 6ff6a696c2..cd409659d5 100644 --- a/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ko-KR/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### Introduction -This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. +This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts. 🙌 @@ -49,7 +49,7 @@ To get an idea of what your Checks API CI server will do when you've completed t ### 빌드전 요구 사양 -Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details. +Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details. You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app. @@ -203,7 +203,7 @@ Great! You've told GitHub to create a check run. You can see the check run statu ### Step 1.4. Updating a check run -When your `create_check_run` method runs, it asks GitHub to create a new check run. When Github finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check. +When your `create_check_run` method runs, it asks GitHub to create a new check run. When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check. You'll want to update your event handler to look for the `created` action. While you're updating the event handler, you can add a conditional for the `rerequested` action. When someone re-runs a single test on GitHub by clicking the "Re-run" button, GitHub sends the `rerequested` check run event to your app. When a check run is `rerequested`, you'll want to start the process all over and create a new check run. diff --git a/translations/ko-KR/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/ko-KR/content/developers/apps/migrating-oauth-apps-to-github-apps.md index b0b4f2866a..7caf549939 100644 --- a/translations/ko-KR/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/ko-KR/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -52,7 +52,7 @@ GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/under #### Register a new GitHub App -Once you've decided to make the switch to Github Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). +Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). #### Determine the permissions your app requires @@ -62,7 +62,7 @@ In your GitHub App's settings, you can specify whether your app needs `No Access #### Subscribe to webhooks -After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a Github App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. +After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. #### Understand the different methods of authentication diff --git a/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md index 3e3b63adf0..bd41bd8f96 100644 --- a/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/ko-KR/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,7 +42,7 @@ This callback request will send you a new access token and a new refresh token. { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" diff --git a/translations/ko-KR/content/developers/apps/suspending-a-github-app-installation.md b/translations/ko-KR/content/developers/apps/suspending-a-github-app-installation.md index bccc484a16..86da72d047 100644 --- a/translations/ko-KR/content/developers/apps/suspending-a-github-app-installation.md +++ b/translations/ko-KR/content/developers/apps/suspending-a-github-app-installation.md @@ -5,6 +5,8 @@ redirect_from: - /apps/managing-github-apps/suspending-a-github-app-installation versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% note %} diff --git a/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index ff81fb5871..3af1dcdda1 100644 --- a/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -14,7 +14,7 @@ versions: {% warning %} -If you offer a GitHub App in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate OAuth App to support this flow. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. +If you offer a {% data variables.product.prodname_github_app %} in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate {% data variables.product.prodname_oauth_app %} to support this flow. See "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endwarning %} @@ -24,7 +24,7 @@ Before a customer purchases your {% data variables.product.prodname_marketplace The customer completes the purchase by clicking **Complete order and begin installation**. -GitHub then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. +{% data variables.product.product_name %} then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. Read the `effective_date` and `marketplace_purchase` object from the `marketplace_purchase` webhook to determine which plan the customer purchased, when the billing cycle starts, and when the next billing cycle begins. @@ -34,27 +34,27 @@ See "[{% data variables.product.prodname_marketplace %} webhook events](/marketp ### Step 2. 설치 -If your app is a GitHub App, GitHub prompts the customer to select which repositories the app can access when they purchase it. GitHub then installs the app on the account the customer selected and grants access to the selected repositories. +If your app is a {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} prompts the customer to select which repositories the app can access when they purchase it. {% data variables.product.product_name %} then installs the app on the account the customer selected and grants access to the selected repositories. -At this point, if you specified a **Setup URL** in your GitHub App settings, Github will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your GitHub App. +At this point, if you specified a **Setup URL** in your {% data variables.product.prodname_github_app %} settings, {% data variables.product.product_name %} will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your {% data variables.product.prodname_github_app %}. {% note %} -**Note:** The **Setup URL** is described as optional in GitHub App settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. +**Note:** The **Setup URL** is described as optional in {% data variables.product.prodname_github_app %} settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. {% endnote %} -If your app is an OAuth App, GitHub does not install it anywhere. Instead, GitHub redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). +If your app is an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} does not install it anywhere. Instead, {% data variables.product.product_name %} redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). -When a customer purchases an OAuth App, GitHub redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. +When a customer purchases an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. ### Step 3. Authorization When a customer purchases your app, you must send the customer through the OAuth authorization flow: -* If your app is a GitHub App, begin the authorization flow as soon as GitHub redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +* If your app is a {% data variables.product.prodname_github_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -* If your app is an OAuth App, begin the authorization flow as soon as GitHub redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/)." +* If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)." For either type of app, the first step is to redirect the customer to https://github.com/login/oauth/authorize. diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md index 19b032ae1d..72a0a1bda5 100644 --- a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -16,7 +16,7 @@ Repl.it is an online integrated development environment (IDE) that supports mult The first time the student clicks the button to visit Repl.it, the student must sign into Repl.it with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on Repl.it. -For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/misc/quick-start#the-repl-environment). +For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/repls/quick-start#the-repl-environment). For group assignments, students can use Repl.it Multiplayer to work collaboratively. For more information, see the [Repl.it Multiplayer](https://repl.it/site/multiplayer) website. diff --git a/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md index 359935372b..2df2bac24d 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -3,6 +3,7 @@ title: About Dependabot version updates intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the packages you use updated to the latest versions.' redirect_from: - /github/administering-a-repository/about-dependabot + - /github/administering-a-repository/about-github-dependabot - /github/administering-a-repository/about-github-dependabot-version-updates versions: free-pro-team: '*' @@ -14,9 +15,9 @@ versions: {% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on. -You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file in to your repository. The configuration file specifies the location of the manifest, or other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository, rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary. +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary. -When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to directly replace the outdated dependency with the new version. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)." +When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)." If you enable security updates, {% data variables.product.prodname_dependabot %} also raises pull requests to update vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." diff --git a/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md b/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md index c235c019e6..869f97b454 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-protected-branches.md @@ -82,12 +82,12 @@ After enabling required status checks, all required status checks must pass befo {% endnote %} -You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging. +You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up to date with the base branch before merging. | Type of required status check | Setting | Merge requirements | Considerations | | ----------------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Strict** | The **Require branches to be up-to-date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch. | -| **Loose** | The **Require branches to be up-to-date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. | +| **Strict** | The **Require branches to be up to date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch. | +| **Loose** | The **Require branches to be up to date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. | | **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes. | For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." diff --git a/translations/ko-KR/content/github/administering-a-repository/about-securing-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/about-securing-your-repository.md index 3ff44718d7..1b85579495 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-securing-your-repository.md @@ -14,6 +14,8 @@ The first step to securing a repository is to set up who can see and modify your {% data variables.product.prodname_dotcom %} has a growing set of security features that help you keep your code secure. You can find these on the **Security** tab for your repository. +#### Available for all repositories + {% if currentVersion == "free-pro-team@latest" %} - **Security policy** @@ -43,15 +45,23 @@ Use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %} + +These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} + - **{% data variables.product.prodname_code_scanning_capc %} alerts** Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." - **Detected secrets** -View any secrets that - {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." - {% endif %} + {% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else if %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +- **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 "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +{% endif %} ### Exploring dependencies {% data variables.product.prodname_dotcom %}'s dependency graph allows you to explore: @@ -59,6 +69,6 @@ View any secrets that * Ecosystems and packages that your repository depends on * Repositories and packages that depend on your repository -You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. +You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. {% if currentVersion == "free-pro-team@latest" %}Enabling the dependency graph also enables {% data variables.product.prodname_dotcom %} to run dependency reviews of pull requests.{% endif %} You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." diff --git a/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md index 49fe064a26..fad691c71b 100644 --- a/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md +++ b/translations/ko-KR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -27,13 +27,13 @@ versions: {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) 5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) 6. When you enable {% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. - ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png) + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} 4. To the right of " {% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index e19203c066..5ff425d08d 100644 --- a/translations/ko-KR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -4,13 +4,12 @@ intro: "You can allow or disallow auto-merge for pull requests in your repositor product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' permissions: People with maintainer permissions can manage auto-merge for pull requests in a repository. --- -{% data reusables.pull_requests.auto-merge-release-phase %} - If you allow auto-merge for pull requests in your repository, people can configure individual pull requests in the repository to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Under "Merge button", select or deselect **Allow auto-merge**. ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) \ No newline at end of file +1. Under "Merge button", select or deselect **Allow auto-merge**. ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) diff --git a/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index 2fd7c6f98d..cd605012a6 100644 --- a/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -33,10 +33,15 @@ You can manage the security and analysis features for your {% if currentVersion {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} 4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. -{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} +**Note:** If you disable + + {% data variables.product.prodname_GH_advanced_security %}, both {% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail. + {% endnote %} + + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) {% endif %} diff --git a/translations/ko-KR/content/github/administering-a-repository/securing-your-repository.md b/translations/ko-KR/content/github/administering-a-repository/securing-your-repository.md index 5a92993859..df0cafb217 100644 --- a/translations/ko-KR/content/github/administering-a-repository/securing-your-repository.md +++ b/translations/ko-KR/content/github/administering-a-repository/securing-your-repository.md @@ -6,5 +6,6 @@ redirect_from: - /articles/securing-your-repository versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- diff --git a/translations/ko-KR/content/github/administering-a-repository/setting-repository-visibility.md b/translations/ko-KR/content/github/administering-a-repository/setting-repository-visibility.md index 4e0753bce3..93e718f022 100644 --- a/translations/ko-KR/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/ko-KR/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,7 +24,7 @@ We recommend reviewing the following caveats before you change the visibility of * If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} * If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %} * Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} * {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %} diff --git a/translations/ko-KR/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/ko-KR/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md index 9276fb3ab2..2882dfc81e 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md +++ b/translations/ko-KR/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md @@ -33,14 +33,18 @@ If you're using a GPG key that matches your committer identity and your verified Comment: GitHub key Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? ``` -7. Enter `O` to save your selections. +7. Enter `O` to confirm your selections. 8. Enter your key's passphrase. -9. Enter `gpg --armor --export GPG key ID`, substituting in the GPG key ID you'd like to use. In the following example, the GPG key ID is `3AA5C34371567BD2`: +9. Enter `gpg> save` to save the changes + ```shell + $ gpg> save + ``` +10. Enter `gpg --armor --export GPG key ID`, substituting in the GPG key ID you'd like to use. In the following example, the GPG key ID is `3AA5C34371567BD2`: ```shell $ gpg --armor --export 3AA5C34371567BD2 # Prints the GPG key, in ASCII armor format ``` -10. Upload the GPG key by [adding it to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account). +11. Upload the GPG key by [adding it to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account). ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index 378da8df6d..ebdf5698ed 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -4,10 +4,9 @@ intro: 'You can increase development velocity by enabling auto-merge for a pull product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' --- -{% data reusables.pull_requests.auto-merge-release-phase %} - ### About auto-merge If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks. diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index 2feea860ff..9e47aecdff 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -9,7 +9,6 @@ versions: github-ae: '*' --- - ### About pull request merges In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. By default, any pull request can be merged at any time, unless the head branch is in conflict with the base branch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index 97cf8f92a7..9743ecfb3e 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -23,7 +23,7 @@ When someone with admin or owner permissions has enabled required reviews, they {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If a team has enabled code review assignments, the individual approvals won't satisfy the requirement for code owner approval in a protected branch. For more information, see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}. diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index f2b6b52495..4b1540a7ce 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -22,7 +22,7 @@ If {% data variables.product.prodname_code_scanning %} finds a potential vulnera To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/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)." +To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." ### About {% data variables.product.prodname_codeql %} diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index 20b3fb7313..eea8b54414 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -18,7 +18,7 @@ You can run {% data variables.product.prodname_code_scanning %} within {% data v 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)." +Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} @@ -26,7 +26,7 @@ Before you can configure {% data variables.product.prodname_code_scanning %} for ### 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_. +{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added 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) @@ -134,7 +134,7 @@ The default {% data variables.product.prodname_codeql_workflow %} file contains {% 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. +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 set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix. ```yaml jobs: diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 543e1a6dc0..839a098784 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -134,19 +134,22 @@ Attempts to build the code for the compiled languages C/C++, C#, and Java. For t Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_location %}. -| Flag | 필수 사항 | Input value | -| -------------------------------- |:-----:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--repository` | ✓ | 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. | +| Flag | 필수 사항 | Input value | +| ---------------------------------- |:-----:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `--repository` | ✓ | 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. | +| `--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. | +| `--threads` | | Number of threads to use when running queries. The default is to use all available cores. | +| `--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. | #### `업로드` diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md index 8ddfc0b163..d7994759b0 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md @@ -17,7 +17,7 @@ versions: ### About the {% data variables.product.prodname_codeql_workflow %} and compiled languages -You enable {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.product.prodname_codeql_workflow %}. 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)." +You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.product.prodname_codeql_workflow %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} For general information about configuring diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md index 0ccb22e86c..eb76999317 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md @@ -14,7 +14,7 @@ versions: {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %} {% link_in_list /about-code-scanning %} {% link_in_list /triaging-code-scanning-alerts-in-pull-requests %} - {% link_in_list /enabling-code-scanning-for-a-repository %} + {% link_in_list /setting-up-code-scanning-for-a-repository %} {% link_in_list /managing-code-scanning-alerts-for-your-repository %} {% link_in_list /configuring-code-scanning %} {% link_in_list /configuring-the-codeql-workflow-for-compiled-languages %} diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 10c720382a..5fe8e75f8f 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -16,7 +16,7 @@ redirect_from: ### About alerts from {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[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)." +You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." @@ -28,7 +28,7 @@ Each alert highlights a problem with the code and the name of the tool that iden ![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) -If you enable {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information. +If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information. When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users. @@ -65,7 +65,7 @@ Closing an alert is a way to resolve an alert that you don't think needs to be f ### Dismissing or deleting alerts -There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have enabled a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have enabled {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab. +There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab. Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab. @@ -127,5 +127,5 @@ If a project has multiple alerts that you want to dismiss for the same reason, y ### 더 읽을거리 - "[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)" -- "[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)" +- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" - "[About integration with {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)" diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 6ceca9cca4..1b2ded94e4 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -24,7 +24,7 @@ If you use a continuous integration or continuous delivery/deployment (CI/CD) sy {% 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)." +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 "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-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. diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 464bb26bf1..4c1fcbd24c 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -97,7 +97,6 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr | `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). | -| `suppressions[].state` | **Optional.** When the `state` is set to `accepted`, {% data variables.product.prodname_code_scanning %} will update the state of the result to `Closed` on {% data variables.product.prodname_dotcom %}. | #### `location` object diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md new file mode 100644 index 0000000000..0b609aa322 --- /dev/null +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -0,0 +1,117 @@ +--- +title: Setting up code scanning for a repository +shortTitle: Setting up code scanning +intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.' +redirect_from: + - /github/managing-security-vulnerabilities/configuring-automated-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} + +### Options for setting up {% data variables.product.prodname_code_scanning %} + +You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to 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 %} + +### Setting up {% 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 %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/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) +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. As a result, {% data variables.product.prodname_code_scanning %} will now commence. + +### 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. 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. + +### 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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. + + ![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 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. + +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, 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 %}. + +### 다음 단계 + +After setting up {% 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 set up {% 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/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index b2eded39f1..626cd99e0d 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -15,7 +15,7 @@ versions: 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, 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 notices and the check succeeds. If your pull request targets a protected branch that has been enabled for {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." +If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, 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 notices and the check succeeds. 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 you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index e11f4f42b6..44cc99921c 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -75,7 +75,7 @@ When ### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% 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 %} +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](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} By default, we notify people with admin permissions in the affected repositories about new @@ -89,6 +89,11 @@ We send security alerts to people with admin permissions in the affected reposit {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} 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" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +You can also see all the +{% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in 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#viewing-your-vulnerable-repositories)." +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md index 4b01db6af5..91a423a855 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -24,7 +24,7 @@ The severity level is one of four possible levels defined in the [Common Vulnera - 높음 - Critical -The {% data variables.product.prodname_advisory_database %} uses CVSS version 3.0 standards and the CVSS levels described above. {% data variables.product.product_name %} doesn't publish CVSS scores. +The {% data variables.product.prodname_advisory_database %} uses CVSS version 3.0 standards and the CVSS levels described above. {% data reusables.repositories.github-security-lab %} @@ -41,24 +41,39 @@ The database is also accessible using the GraphQL API. For more information, see {% endnote %} ### Searching the {% data variables.product.prodname_advisory_database %} -You can search the database, and use qualifiers to narrow your search to advisories created on a certain date, in a specific ecosystem, or in a particular library. + +You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | 예시 | -| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | -| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | -| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | -| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | -| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | -| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | -| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | -| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | -| `created:YYYY-MM-DD` | [**created:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2019-10-31) will show only advisories created on this date. | -| `updated:YYYY-MM-DD` | [**updated:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2019-10-31) will show only advisories updated on this date. | +| Qualifier | 예시 | +| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `GHSA-ID` | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | +| `CVE-ID` | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | +| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | +| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | +| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | +| `cwe:ID` | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | +| `credit:USERNAME` | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | +| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | +| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | +| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | +| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | +| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | +| `created:YYYY-MM-DD` | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | +| `updated:YYYY-MM-DD` | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. | + +### Viewing your vulnerable repositories + +For any vulnerability in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories have a {% data variables.product.prodname_dependabot %} alert for that vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)." + +1. Navigate to https://github.com/advisories. +2. Click an advisory. +3. At the top of the advisory page, click **Dependabot alerts**. ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png) +4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) +5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name. ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index 5c4f268ece..6d51cff47b 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -12,6 +12,8 @@ versions: {% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." +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 %} usage beyond the amounts including with your account. 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)." + Minutes reset every month, while storage usage does not. | 제품 | Storage | Minutes (per month) | diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 838a947290..593427eec1 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.package_registry.container-registry-beta-billing-note %} +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_registry %} usage beyond the amounts including with your account. 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 transfer resets every month, while storage usage does not. | 제품 | Storage | Data transfer (per month) | diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 8ae1262da6..d60c00f961 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} 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)." +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 %} usage beyond the amounts including with your account. 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)." + As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and creates workflow artifacts that increase your storage usage for the month from 1.9GB to 2.1GB, you will use slightly more storage than the 2GB your product includes. Because you have not enabled overages, your next attempt to create a workflow artifact will fail. You will not receive a bill for the 0.1GB overage that month. However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index a89aca74c9..b7e1e4fde1 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} 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)." +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_registry %} usage beyond the amounts including with your account. 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)." + As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and publishes a new version of a private package that increases your storage usage for the month from 1.9GB to 2.1GB, publishing the version will use slightly more than the 2GB your product includes. Because you have not enabled overages, your next attempt to publish a version of the package will fail. You will not receive a bill for the 0.1GB overage that month. However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 8e1a5def02..e52fb79315 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -23,8 +23,13 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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. +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. +{% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@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.{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) {% endif %} @@ -42,24 +47,21 @@ You can enable or disable features for all repositories. {% if currentVersion == 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)." 1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) {% endif %} 2. Optionally, enable the feature by default for new repositories in your organization. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) {% endif %} -1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. - {% if currentVersion == "free-pro-team@latest" %} +3. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) {% endif %} @@ -68,10 +70,9 @@ You can enable or disable features for all repositories. {% if currentVersion == 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)." 1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories {% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![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 %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) {% endif %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 36b0f7cd4c..7fa715be0a 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -70,7 +70,7 @@ In addition to managing organization-level settings, organization owners have ad {% 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** |{% if currentVersion == "free-pro-team@latest" %} +| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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** | @@ -150,8 +150,8 @@ In this section, you can find the repository permission levels required for secu | Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | | [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/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** | -| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% 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 | | | | | **X** | | [View dependency reviews](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | [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** | diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md new file mode 100644 index 0000000000..ea9b3d4b19 --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md @@ -0,0 +1,40 @@ +--- +title: Connecting an Azure subscription to your enterprise +intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the included amounts for your enterprise.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise +versions: + free-pro-team: '*' +--- + +### About Azure subscriptions and {% data variables.product.product_name %} + +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 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) and "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." + +After you connect an Azure subscription, you can also manage your spending limit. For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)" and "[Managing your spending limit for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)." + +### Connecting your Azure subscription to your enterprise account + +To connect your Azure subscription, you must have owner permissions to the subscription. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Payment Information", click **Add Azure Subscription**. +1. To sign in to your Microsoft account, follow the prompts. +1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**. +1. Under "Select a subscription", select the Azure Subscription ID that you want to connect to your enterprise. +1. Click **Connect**. + +### Disconnecting your Azure subscription from your enterprise account + +After you disconnect your Azure subscription from your enterprise account, your usage can no longer exceed the amounts included with your plan. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. +1. Review the prompt, then click **Remove**. 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 4dae4a37df..a0f04ad09c 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 @@ -18,6 +18,7 @@ versions: {% link_in_list /about-enterprise-accounts %} {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %} {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %} + {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %} {% topic_link_in_list /managing-users-in-your-enterprise %} {% link_in_list /roles-in-an-enterprise %} {% link_in_list /inviting-people-to-manage-your-enterprise %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md index 1b84c0d34c..aa2bcbfa9a 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md @@ -31,7 +31,7 @@ Enterprise owners have complete control over the enterprise and can take every a Enterprise owners cannot access organization settings or content unless they are made an organization owner or given direct access to an organization-owned repository. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. -You can add as many enterprise owners as you'd like to your enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. +An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. ### Enterprise members @@ -52,7 +52,7 @@ Billing managers only have access to your enterprise's billing settings. Billing - View a list of billing managers - Add or remove other billing managers -Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}. +Billing managers will only consume a license if they are an owner or member of at least one organization within the enterprise. Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}. ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 3b2c0ceb76..14d76e4172 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -15,6 +15,8 @@ versions: Enterprise accounts are currently available to {% data variables.product.prodname_enterprise %} customers paying by invoice. Billing for all of the organizations and {% data variables.product.prodname_ghe_server %} instances connected to your enterprise account are aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services (including paid licenses in organizations, {% data variables.large_files.product_name_long %} data packs, and subscriptions for {% data variables.product.prodname_marketplace %} apps). +{% if currentVersion == "free-pro-team@latest" %}{% 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)."{% endif %} + For more information about managing billing managers, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." ### Viewing the subscription and usage for your enterprise account diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index 5a4271c826..f461f9cb21 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -50,7 +50,7 @@ The repository owner has full control of the repository. In addition to the acti | Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | | Archive the repository | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | -| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" | +| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} | Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %} ### Collaborator access for a repository owned by a user account diff --git a/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index e466479b76..8755e2560b 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -25,8 +25,6 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages % {% 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 %} @@ -36,6 +34,8 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages % {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% 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 diff --git a/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site.md b/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site.md index 1816e06364..036b40dae8 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site.md +++ b/translations/ko-KR/content/github/working-with-github-pages/creating-a-github-pages-site.md @@ -20,8 +20,6 @@ versions: {% 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 %} @@ -33,6 +31,8 @@ versions: {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% data reusables.pages.navigate-site-repo %} {% data reusables.pages.decide-publishing-source %} 3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source. diff --git a/translations/ko-KR/content/rest/overview/libraries.md b/translations/ko-KR/content/rest/overview/libraries.md index 2d0f25d9c9..51935046da 100644 --- a/translations/ko-KR/content/rest/overview/libraries.md +++ b/translations/ko-KR/content/rest/overview/libraries.md @@ -57,7 +57,7 @@ Library name | Repository | |---|---| **NodeJS GitHub library**| [pksunkara/octo ### Julia -Library name | Repository | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl) +Library name | Repository | |---|---| **GitHub.jl**|[WestleyArgentum/GitHub.jl](https://github.com/WestleyArgentum/GitHub.jl) ### OCaml @@ -65,11 +65,11 @@ Library name | Repository | |---|---| **ocaml-github**|[mirage/ocaml-github](htt ### Perl -Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub) +Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub) ### PHP -Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI) +Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GitHubAPI](https://github.com/FlexyProject/GitHubAPI) ### Python diff --git a/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md b/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md index 150978d285..c126d713e8 100644 --- a/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md @@ -129,7 +129,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar > { > "message": "Bad credentials", -> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -141,7 +141,7 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f > 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" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -358,7 +358,7 @@ If you exceed the rate limit, an error response returns: > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#rate-limiting" > } ``` @@ -403,7 +403,7 @@ If your application triggers this rate limit, you'll receive an informative resp > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#abuse-rate-limits" > } ``` diff --git a/translations/ko-KR/content/rest/reference/repos.md b/translations/ko-KR/content/rest/reference/repos.md index 538bc10391..b9a96f72f7 100644 --- a/translations/ko-KR/content/rest/reference/repos.md +++ b/translations/ko-KR/content/rest/reference/repos.md @@ -141,7 +141,7 @@ Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth- ### Inactive deployments -When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. +When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository to the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. You can communicate that a transient environment no longer exists by setting its `state` to `inactive`. Setting the `state` to `inactive` shows the deployment as `destroyed` in {% data variables.product.prodname_dotcom %} and removes access to it. diff --git a/translations/ko-KR/data/reusables/actions/enterprise-beta.md b/translations/ko-KR/data/reusables/actions/enterprise-beta.md index b10237e282..0c674122af 100644 --- a/translations/ko-KR/data/reusables/actions/enterprise-beta.md +++ b/translations/ko-KR/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,12 @@ {% if enterpriseServerVersions contains currentVersion 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 "[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)." +**Note:** {% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. The beta has ended. {% data variables.product.prodname_actions %} is now generally available in {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +
+ +- For more information about upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." +- For more information about configuring {% data variables.product.prodname_actions %} after you upgrade, see the [documentation for {% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server). {% endnote %} {% endif %} diff --git a/translations/ko-KR/data/reusables/actions/enterprise-common-prereqs.md b/translations/ko-KR/data/reusables/actions/enterprise-common-prereqs.md index ee9ba1dca8..3a9923ae8e 100644 --- a/translations/ko-KR/data/reusables/actions/enterprise-common-prereqs.md +++ b/translations/ko-KR/data/reusables/actions/enterprise-common-prereqs.md @@ -1,4 +1,4 @@ -* {% data reusables.actions.enterprise-hardware-considerations %} +* Review the hardware requirements for {% data variables.product.prodname_actions %}. 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#review-hardware-considerations)." * TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." {% note %} diff --git a/translations/ko-KR/data/reusables/actions/enterprise-hardware-considerations.md b/translations/ko-KR/data/reusables/actions/enterprise-hardware-considerations.md index 24c077bbae..98ac65f438 100644 --- a/translations/ko-KR/data/reusables/actions/enterprise-hardware-considerations.md +++ b/translations/ko-KR/data/reusables/actions/enterprise-hardware-considerations.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "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)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. +If you {% if currentVersion == "enterprise-server@2.22" %} configured the beta of{% else %} configure{% endif %} {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, we recommend that you provision additional CPU and memory resources. The additional resources you need to provision depend on the number of workflows your users run concurrently, and the overall levels of activity for your instance. diff --git a/translations/ko-KR/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/ko-KR/data/reusables/advanced-security/note-org-enable-uses-seats.md index 48f3c5a99a..733e8e8a97 100644 --- a/translations/ko-KR/data/reusables/advanced-security/note-org-enable-uses-seats.md +++ b/translations/ko-KR/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -1,7 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. This option controls access to all {% data variables.product.prodname_advanced_security %} features including {% if currentVersion == "free-pro-team@latest" %}dependency review,{% endif %} {% data variables.product.prodname_code_scanning %}, and {% data variables.product.prodname_secret_scanning %}. {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/code-scanning/enabling-options.md b/translations/ko-KR/data/reusables/code-scanning/enabling-options.md index 3ef6731b26..bbbd1a7893 100644 --- a/translations/ko-KR/data/reusables/code-scanning/enabling-options.md +++ b/translations/ko-KR/data/reusables/code-scanning/enabling-options.md @@ -15,7 +15,7 @@ - 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"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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"). @@ -25,7 +25,7 @@ - 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 %}"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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 %}"). 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 e5b61bf344..1865510660 100644 --- a/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md @@ -8,7 +8,7 @@ The following table shows, for each package manager: | --------------- | ---------------- | ------------------------- |:--------------------:|:---------:| | 번들러 | `bundler` | v1 | | **✓** | | Cargo | `cargo` | v1 | **✓** | | -| Composer | `composer` | v1,v2 | **✓** | | +| Composer | `composer` | v1, v2 | **✓** | | | Docker | `docker` | v1 | **✓** | | | Elixir | `mix` | v1 | **✓** | | | Elm | `elm` | v0.18, v0.19 | **✓** | | @@ -17,7 +17,7 @@ The following table shows, for each package manager: | Go modules | `gomod` | v1 | **✓** | **✓** | | Gradle | `gradle` | see (A) below | **✓** | | | Maven | `maven` | see (B) below | **✓** | | -| npm | `npm` | v6 | **✓** | | +| npm | `npm` | v6, v7 | **✓** | | | NuGet | `nuget` | <= 4.8.
see (C) below | **✓** | | | pip | `pip` | v20 | | | | pipenv | `pip` | <= 2018.11.26 | | | diff --git a/translations/ko-KR/data/reusables/desktop/choose-clone-repository.md b/translations/ko-KR/data/reusables/desktop/choose-clone-repository.md index 45deab6ea4..41f4b6a914 100644 --- a/translations/ko-KR/data/reusables/desktop/choose-clone-repository.md +++ b/translations/ko-KR/data/reusables/desktop/choose-clone-repository.md @@ -1 +1,13 @@ 1. In the **File** menu, click **Clone Repository**. + + {% mac %} + + ![Clone menu option in the Mac app](/assets/images/help/desktop/clone-file-menu-mac.png) + + {% endmac %} + + {% windows %} + + ![Clone menu option in the Windows app](/assets/images/help/desktop/clone-file-menu-windows.png) + + {% endwindows %} diff --git a/translations/ko-KR/data/reusables/desktop/choose-local-path.md b/translations/ko-KR/data/reusables/desktop/choose-local-path.md new file mode 100644 index 0000000000..8bf8a7ac5f --- /dev/null +++ b/translations/ko-KR/data/reusables/desktop/choose-local-path.md @@ -0,0 +1,13 @@ +1. Click **Choose...** and navigate to a local path where you want to clone the repository. + + {% mac %} + + ![The choose button](/assets/images/help/desktop/clone-choose-button-mac.png) + + {% endmac %} + + {% windows %} + + ![The choose button](/assets/images/help/desktop/clone-choose-button-win.png) + + {% endwindows %} diff --git a/translations/ko-KR/data/reusables/desktop/click-clone.md b/translations/ko-KR/data/reusables/desktop/click-clone.md new file mode 100644 index 0000000000..d291246ebf --- /dev/null +++ b/translations/ko-KR/data/reusables/desktop/click-clone.md @@ -0,0 +1,14 @@ +1. Click **Clone**. + + {% mac %} + + ![The clone button](/assets/images/help/desktop/clone-button-mac.png) + + {% endmac %} + + {% windows %} + + ![The clone button](/assets/images/help/desktop/clone-button-win.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/desktop/cloning-location-tab.md b/translations/ko-KR/data/reusables/desktop/cloning-location-tab.md index 8752592c0e..e4610d9f88 100644 --- a/translations/ko-KR/data/reusables/desktop/cloning-location-tab.md +++ b/translations/ko-KR/data/reusables/desktop/cloning-location-tab.md @@ -1 +1,13 @@ 1. Click the tab that corresponds to the location of the repository you want to clone. You can also click **URL** to manually enter the repository location. + + {% mac %} + + ![Location tabs in the Clone a repository menu](/assets/images/help/desktop/choose-repository-location-mac.png) + + {% endmac %} + + {% windows %} + + ![Location tabs in the Clone a repository menu](/assets/images/help/desktop/choose-repository-location-win.png) + + {% endwindows %} diff --git a/translations/ko-KR/data/reusables/desktop/cloning-repository-list.md b/translations/ko-KR/data/reusables/desktop/cloning-repository-list.md index 37d26e3039..97a7f7a894 100644 --- a/translations/ko-KR/data/reusables/desktop/cloning-repository-list.md +++ b/translations/ko-KR/data/reusables/desktop/cloning-repository-list.md @@ -1 +1,14 @@ 1. Choose the repository you want to clone from the list. + + + {% mac %} + + ![Clone a repository list](/assets/images/help/desktop/clone-a-repository-list-mac.png) + + {% endmac %} + + {% windows %} + + ![Clone a repository list](/assets/images/help/desktop/clone-a-repository-list-win.png) + + {% endwindows %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/desktop/fork-type-prompt.md b/translations/ko-KR/data/reusables/desktop/fork-type-prompt.md new file mode 100644 index 0000000000..1067dab748 --- /dev/null +++ b/translations/ko-KR/data/reusables/desktop/fork-type-prompt.md @@ -0,0 +1,42 @@ +1. If you plan to use this fork for contributing to the original upstream repository, click **To contribute to the parent project**. + + {% mac %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/mac-fork-options-prompt.png) + + {% endmac %} + + {% windows %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/windows-fork-options-prompt.png) + + {% endwindows %} + +2. If you plan to use this fork for a project not connected to the upstream, click **For my own purposes**. + + {% mac %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/mac-fork-own-purposes.png) + + {% endmac %} + + {% windows %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/windows-fork-own-purposes.png) + + {% endwindows %} + +3. Click **Continue**. + + {% mac %} + + ![The continue button](/assets/images/help/desktop/mac-forking-continue.png) + + {% endmac %} + + {% windows %} + + ![The continue button](/assets/images/help/desktop/windows-forking-continue.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/desktop/open-repository-settings.md b/translations/ko-KR/data/reusables/desktop/open-repository-settings.md new file mode 100644 index 0000000000..5e298edc85 --- /dev/null +++ b/translations/ko-KR/data/reusables/desktop/open-repository-settings.md @@ -0,0 +1,14 @@ +1. Open the **Repository** menu, then click **Repository settings...**. + + {% mac %} + + ![Repository settings menu option in the Mac app](/assets/images/help/desktop/mac-repository-settings.png) + + {% endmac %} + + {% windows %} + + ![Repository settings menu option in the Windows app](/assets/images/help/desktop/windows-repository-settings.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/desktop/select-fork-behavior.md b/translations/ko-KR/data/reusables/desktop/select-fork-behavior.md new file mode 100644 index 0000000000..05785064e3 --- /dev/null +++ b/translations/ko-KR/data/reusables/desktop/select-fork-behavior.md @@ -0,0 +1,28 @@ +1. Click **Fork behavior**, then select how you want to use the fork. + + {% mac %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-menu-contribute.png) + + {% endmac %} + + {% windows %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-menu-contribute.png) + + {% endwindows %} + +2. Click **Save**. + + {% mac %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-save.png) + + {% endmac %} + + {% windows %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-save.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md b/translations/ko-KR/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md new file mode 100644 index 0000000000..63fa9473e7 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md @@ -0,0 +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 including with your account. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/payment-information-tab.md b/translations/ko-KR/data/reusables/enterprise-accounts/payment-information-tab.md new file mode 100644 index 0000000000..4de0966ad7 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/payment-information-tab.md @@ -0,0 +1 @@ +1. Under "Billing", click **Payment information**. diff --git a/translations/ko-KR/data/reusables/enterprise_installation/about-adjusting-resources.md b/translations/ko-KR/data/reusables/enterprise_installation/about-adjusting-resources.md new file mode 100644 index 0000000000..2d6c2fe4e6 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise_installation/about-adjusting-resources.md @@ -0,0 +1 @@ +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)." diff --git a/translations/ko-KR/data/reusables/enterprise_installation/aws-supported-instance-types.md b/translations/ko-KR/data/reusables/enterprise_installation/aws-supported-instance-types.md index 5cf0c50693..e5b77c7385 100644 --- a/translations/ko-KR/data/reusables/enterprise_installation/aws-supported-instance-types.md +++ b/translations/ko-KR/data/reusables/enterprise_installation/aws-supported-instance-types.md @@ -1,37 +1,13 @@ -{% data variables.product.prodname_ghe_server %} is supported on the following EC2 instance types. For more information, see [the AWS EC2 instance type overview page](http://aws.amazon.com/ec2/instance-types/). +{% data variables.product.prodname_ghe_server %} is supported on the following EC2 instance sizes. For more information, see [the AWS EC2 instance type overview page](http://aws.amazon.com/ec2/instance-types/). -| EC2 instance type | Model | -| ----------------- | ---------------------------------- | -| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | - -| EC2 instance type | Model | -| ----------------- | ---------------------------------- | -| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | - -| EC2 instance type | Model | -| ----------------- | -------------------------------------------------------------------- | -| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | - -| EC2 instance type | Model | -| ----------------- | --------------------- | -| M3 | m3.xlarge, m3.2xlarge | - -| EC2 instance type | Model | -| ----------------- | ----------------------------------------------------------- | -| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | - -| EC2 instance type | Model | -| ----------------- | --------------------------------------------------------------------- | -| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | - -| EC2 instance type | Model | -| ----------------- | -------------------------------------------------------------------- | -| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | - -| EC2 instance type | Model | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} - -| EC2 instance type | Model | -| ----------------- | ------------------------ | -| X1 | x1.16xlarge, x1.32xlarge | +| 유형 | Size | +|:-- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | +| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | +| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | +| M3 | m3.xlarge, m3.2xlarge | +| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | +| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | +| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | +| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} +| X1 | x1.16xlarge, x1.32xlarge | diff --git a/translations/ko-KR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/ko-KR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 1bdc5adca7..ec895f314d 100644 --- a/translations/ko-KR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/ko-KR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,6 +1,5 @@ - [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} -- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} -- [Optional features](#optional-features){% endif %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %} - [Storage](#storage) - [CPU and memory](#cpu-and-memory) @@ -8,20 +7,7 @@ We recommend different hardware configurations depending on the number of user licenses for {% data variables.product.product_location %}. If you provision more resources than the minimum requirements, your instance will perform and scale better. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - -- You must configure at least one runner for {% data variables.product.prodname_actions %} workflows. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." -- You must configure external blob storage. 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)." -- You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} 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 | Additional vCPUs | Additional memory | - |:----------------------- | ----------------:| -----------------:| - | Light testing | 4 | 30.5 GB | - | 25 | 8 | 61 GB | - | 35 | 16 | 122 GB | - | 100 | 32 | 244 GB | - -{% endif %} +{% data reusables.enterprise_installation.hardware-rec-table %} #### Storage @@ -31,7 +17,7 @@ Your instance requires a persistent data disk separate from the root disk. For m {% if currentVersion ver_gt "enterprise-server@2.21" %} -If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. 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)." +To configure{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you must provide external blob storage. 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)." {% endif %} @@ -39,7 +25,7 @@ You can resize your instance's root disk by building a new instance or using an #### 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. +The CPU and memory resources that {% data variables.product.prodname_ghe_server %} requires depend on the levels of activity for users, automations, and integrations. {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data reusables.actions.enterprise-hardware-considerations %}{% endif %} {% data reusables.enterprise_installation.increasing-cpus-req %} diff --git a/translations/ko-KR/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/ko-KR/data/reusables/enterprise_installation/hardware-rec-table.md index a9ffb7473a..a7310c66fc 100644 --- a/translations/ko-KR/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/ko-KR/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,20 +1,20 @@ -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." +**Note**: If you joined the beta for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} and enabled the features, your instance requires additional hardware resources. 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)." {% endnote %} {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -| User licenses | vCPUs | Memory | Attached storage | Root storage | -|:------------------------------ | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| ------------:| -| Trial, demo, or 10 light users | 2
or [**4**](#optional-features) | 16 GB
or [**32 GB**](#optional-features) | 100 GB
or [**150 GB**](#optional-features) | 200 GB | -| 10 to 3,000 | 4
or [**8**](#optional-features) | 32 GB
or [**48 GB**](#optional-features) | 250 GB
or [**300 GB**](#optional-features) | 200 GB | -| 3,000 to 5000 | 8
or [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | -| 5,000 to 8000 | 12
or [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | -| 8,000 to 10,000+ | 16
or [**20**](#optional-features) | 128 GB
or [**160 GB**](#optional-features) | 1000 GB | 200 GB | +| User licenses | vCPUs | Memory | Attached storage | Root storage | +|:------------------------------ | -----:| ------:| ----------------:| ------------:| +| Trial, demo, or 10 light users | 4 | 32 GB | 150 GB | 200 GB | +| 10 to 3,000 | 8 | 48 GB | 300 GB | 200 GB | +| 3,000 to 5000 | 12 | 64 GB | 500 GB | 200 GB | +| 5,000 to 8000 | 16 | 96 GB | 750 GB | 200 GB | +| 8,000 to 10,000+ | 20 | 160 GB | 1000 GB | 200 GB | {% else %} @@ -28,22 +28,20 @@ {% endif %} -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)." +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +If you plan to configure {% data variables.product.prodname_actions %} for your instance, you should provision additional resources. You must also configure at least one self-hosted runner to execute workflows. 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)." + +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} #### Beta features in {% data variables.product.prodname_ghe_server %} 2.22 -You can sign up for beta features available in {% data variables.product.prodname_ghe_server %} 2.22 such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [release notes for the 2.22 series](https://enterprise.github.com/releases/series/2.22#release-2.22.0) on the {% data variables.product.prodname_enterprise %} website. +{% data variables.product.prodname_ghe_server %} 2.22 offered features in beta, such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [{% data variables.product.prodname_ghe_server %} 2.22 release notes](/enterprise-server@2.22/admin/release-notes#2.22.0). -If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". - -{% elsif currentVersion ver_gt "enterprise-server@2.22" %} - -#### Optional features - -You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. 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)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." - -If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +If you enabled beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". {% endif %} diff --git a/translations/ko-KR/data/reusables/gated-features/auto-merge.md b/translations/ko-KR/data/reusables/gated-features/auto-merge.md index 72a58ba07d..acfb4dddff 100644 --- a/translations/ko-KR/data/reusables/gated-features/auto-merge.md +++ b/translations/ko-KR/data/reusables/gated-features/auto-merge.md @@ -1 +1 @@ -Auto-merge for pull requests 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" %}{% data reusables.gated-features.more-info %}{% endif %} \ No newline at end of file +Auto-merge for pull requests 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 %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/ko-KR/data/reusables/gated-features/code-scanning.md b/translations/ko-KR/data/reusables/gated-features/code-scanning.md index 69e6abf27f..35598cce54 100644 --- a/translations/ko-KR/data/reusables/gated-features/code-scanning.md +++ b/translations/ko-KR/data/reusables/gated-features/code-scanning.md @@ -1 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled. +{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository. +{%- else %} +{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} 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 37caf3e2cc..103252d436 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 @@ -1,8 +1,8 @@ -| Virtual environment | YAML workflow label | -| -------------------- | ---------------------------------- | -| Windows Server 2019 | `windows-latest` or `windows-2019` | -| Ubuntu 20.04 | `ubuntu-20.04` | -| Ubuntu 18.04 | `ubuntu-latest` or `ubuntu-18.04` | -| Ubuntu 16.04 | `ubuntu-16.04` | -| macOS Big Sur 11.0 | `macos-11.0` | -| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | +| Virtual environment | YAML workflow label | +| -------------------- | -------------------------------------------- | +| Windows Server 2019 | `windows-latest` or `windows-2019` | +| Ubuntu 20.04 | `ubuntu-latest` (see note) or `ubuntu-20.04` | +| Ubuntu 18.04 | `ubuntu-latest` (see note) or `ubuntu-18.04` | +| Ubuntu 16.04 | `ubuntu-16.04` | +| macOS Big Sur 11.0 | `macos-11.0` | +| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | diff --git a/translations/ko-KR/data/reusables/github-actions/ubuntu-runner-preview.md b/translations/ko-KR/data/reusables/github-actions/ubuntu-runner-preview.md index 1a3636e0e1..6eb91edc13 100644 --- a/translations/ko-KR/data/reusables/github-actions/ubuntu-runner-preview.md +++ b/translations/ko-KR/data/reusables/github-actions/ubuntu-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The Ubuntu 20.04 virtual environment is currently provided as a preview only. The `ubuntu-latest` YAML workflow label still uses the Ubuntu 18.04 virtual environment. +**Note:** The `ubuntu-latest` label is currently being migrated from the Ubuntu 18.04 virtual environment to Ubuntu 20.04. Specifying the `ubuntu-latest` label during the migration might use either virtual environment. To explicitly use Ubuntu 20.04 or Ubuntu 18.04, specify `ubuntu-20.04` or `ubuntu-18.04`. When the migration is complete, `ubuntu-latest` will use the Ubuntu 20.04 virtual environment. For more information about the migration, see "[Ubuntu-latest workflows will use Ubuntu-20.04](https://github.com/actions/virtual-environments/issues/1816)." {% endnote %} diff --git a/translations/ko-KR/data/reusables/organizations/organizations_include.md b/translations/ko-KR/data/reusables/organizations/organizations_include.md index da902c12ed..766b2394dc 100644 --- a/translations/ko-KR/data/reusables/organizations/organizations_include.md +++ b/translations/ko-KR/data/reusables/organizations/organizations_include.md @@ -6,3 +6,4 @@ Organizations include: - [Nested teams that reflect your company or group's structure](/articles/about-teams) with cascading access permissions and mentions{% if currentVersion != "github-ae@latest" %} - The ability for organization owners to view members' [two-factor authentication (2FA) status](/articles/about-two-factor-authentication) - The option to [require all organization members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} +{% if currentVersion == "free-pro-team@latest" %}- The option to purchase a license for {% data variables.product.prodname_GH_advanced_security %} and use the features on private repositories. {% data reusables.advanced-security.more-info-ghas %}{% endif %} diff --git a/translations/ko-KR/data/reusables/pages/new-or-existing-repo.md b/translations/ko-KR/data/reusables/pages/new-or-existing-repo.md index 4fdcdaf871..bfb5ba3b47 100644 --- a/translations/ko-KR/data/reusables/pages/new-or-existing-repo.md +++ b/translations/ko-KR/data/reusables/pages/new-or-existing-repo.md @@ -1,3 +1,5 @@ If your site is an independent project, you can create a new repository to store your site's source code. If your site is associated with an existing project, you can add the source code {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}to that project's repository, in a `/docs` folder on the default branch or on a different branch.{% else %}for your site to a `gh-pages` branch or a `docs` folder on the `master` branch in that project's repository.{% endif %} For example, if you're creating a site to publish documentation for a project that's already on {% data variables.product.product_name %}, you may want to store the source code for the site in the same repository as the project. +{% if currentVersion == "free-pro-team@latest" %}If the account that owns the repository uses {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_free_team %}, the repository must be public.{% endif %} + If you want to create a site in an existing repository, skip to the "[Creating your site](#creating-your-site)" section. diff --git a/translations/ko-KR/data/reusables/pull_requests/you-can-auto-merge.md b/translations/ko-KR/data/reusables/pull_requests/you-can-auto-merge.md index 410aec2a8e..5da386a3d1 100644 --- a/translations/ko-KR/data/reusables/pull_requests/you-can-auto-merge.md +++ b/translations/ko-KR/data/reusables/pull_requests/you-can-auto-merge.md @@ -1,3 +1,3 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} You can configure a pull request to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md index 444621076f..e8e27494cb 100644 --- a/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/ko-KR/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| 키 | 유형 | 설명 | -| ---- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `동작` | `문자열` | The action that was performed. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | +| 키 | 유형 | 설명 | +| ---- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `동작` | `문자열` | The action that was performed. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | diff --git a/translations/ko-KR/data/variables/action_code_examples.yml b/translations/ko-KR/data/variables/action_code_examples.yml index a1a9e462d7..98b6b4037f 100644 --- a/translations/ko-KR/data/variables/action_code_examples.yml +++ b/translations/ko-KR/data/variables/action_code_examples.yml @@ -24,7 +24,7 @@ - labels - title: Add releases to GitHub - description: Publish Github releases in an action + description: Publish GitHub releases in an action languages: 'Dockerfile, Shell' href: elgohr/Github-Release-Action tags: @@ -32,7 +32,7 @@ - publishing - title: Publish a docker image to Dockerhub - description: A Github Action used to build and publish Docker images + description: A GitHub Action used to build and publish Docker images languages: 'Dockerfile, Shell' href: elgohr/Publish-Docker-Github-Action tags: @@ -123,7 +123,7 @@ - publishing - title: Label your Pull Requests auto-magically (using committed files) - description: Github action to label your pull requests auto-magically (using committed files) + description: GitHub action to label your pull requests auto-magically (using committed files) languages: 'TypeScript, Dockerfile, JavaScript' href: Decathlon/pull-request-labeler-action tags: @@ -132,7 +132,7 @@ - labels - title: Add Label to your Pull Requests based on the author team name - description: Github action to label your pull requests based on the author name + description: GitHub action to label your pull requests based on the author name languages: 'TypeScript, JavaScript' href: JulienKode/team-labeler-action tags: diff --git a/translations/ko-KR/data/variables/product.yml b/translations/ko-KR/data/variables/product.yml index c828481f8a..8dfe7bc55e 100644 --- a/translations/ko-KR/data/variables/product.yml +++ b/translations/ko-KR/data/variables/product.yml @@ -147,10 +147,10 @@ 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://docs.github.com/rest{% elsif enterpriseServerVersions contains currentVersion %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif currentVersion == "github-ae@latest" %}https://docs.github.com/github-ae@latest/rest{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% endif %} #Use this inside command-line code blocks #Enterprise OAuth paths that don't include "/graphql" or "/api/v3" oauth_host_code: >- @@ -159,10 +159,10 @@ device_authorization_url: >- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}[`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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/graphql{% endif %} diff --git a/translations/pt-BR/content/actions/guides/about-service-containers.md b/translations/pt-BR/content/actions/guides/about-service-containers.md index 1a7ada5f13..3d437feaba 100644 --- a/translations/pt-BR/content/actions/guides/about-service-containers.md +++ b/translations/pt-BR/content/actions/guides/about-service-containers.md @@ -10,7 +10,7 @@ versions: enterprise-server: '>=2.22' type: overview topics: - - Containers + - Contêineres - Docker --- diff --git a/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md b/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md index 691710b3c7..bde72bfcbd 100644 --- a/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md +++ b/translations/pt-BR/content/actions/guides/creating-postgresql-service-containers.md @@ -11,7 +11,7 @@ versions: enterprise-server: '>=2.22' type: 'tutorial' topics: - - 'Containers' + - 'Contêineres' - 'Docker' --- diff --git a/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md b/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md index 1c47ed0680..734f8437ac 100644 --- a/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md +++ b/translations/pt-BR/content/actions/guides/creating-redis-service-containers.md @@ -11,7 +11,7 @@ versions: enterprise-server: '>=2.22' type: 'tutorial' topics: - - 'Containers' + - 'Contêineres' - 'Docker' --- diff --git a/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md b/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md index 16887e98f5..82aff05f75 100644 --- a/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md +++ b/translations/pt-BR/content/actions/guides/deploying-to-amazon-elastic-container-service.md @@ -8,7 +8,7 @@ versions: type: 'tutorial' topics: - 'CD' - - 'Containers' + - 'Contêineres' - 'Amazon ECS' --- diff --git a/translations/pt-BR/content/actions/guides/deploying-to-azure-app-service.md b/translations/pt-BR/content/actions/guides/deploying-to-azure-app-service.md index 503d8c6b8a..1ce0d9e13b 100644 --- a/translations/pt-BR/content/actions/guides/deploying-to-azure-app-service.md +++ b/translations/pt-BR/content/actions/guides/deploying-to-azure-app-service.md @@ -8,7 +8,7 @@ versions: type: 'tutorial' topics: - 'CD' - - 'Containers' + - 'Contêineres' - 'Serviço do aplicativo Azure' --- diff --git a/translations/pt-BR/content/actions/guides/deploying-to-google-kubernetes-engine.md b/translations/pt-BR/content/actions/guides/deploying-to-google-kubernetes-engine.md index 9d98112c96..39a06bf0a6 100644 --- a/translations/pt-BR/content/actions/guides/deploying-to-google-kubernetes-engine.md +++ b/translations/pt-BR/content/actions/guides/deploying-to-google-kubernetes-engine.md @@ -8,7 +8,7 @@ versions: type: 'tutorial' topics: - 'CD' - - 'Containers' + - 'Contêineres' - 'Google Kubernetes Engine' --- 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 b67b94a213..f2ac28d038 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 @@ -63,7 +63,7 @@ Existem alguns limites sobre o uso de {% data variables.product.prodname_actions {% data reusables.github-actions.usage-api-requests %} - **Matriz de vagas** - {% data reusables.github-actions.usage-matrix-limits %} -### Sistemas operacionais compatíveis com executores auto-hospedados +### Supported architectures and operating systems for self-hosted runners Os sistemas operacionais a seguir são compatíveis com o aplicativo de execução auto-hospedado. @@ -92,6 +92,14 @@ Os sistemas operacionais a seguir são compatíveis com o aplicativo de execuç - macOS 10.13 (High Sierra) or versão posterior +#### Architectures + +The following processor architectures are supported for the self-hosted runner application. + +- `x64` - Linux, macOS, Windows. +- `ARM64` - Linux only. +- `ARM32` - Linux only. + {% if enterpriseServerVersions contains currentVersion %} ### Comunicação entre executores auto-hospedados e {% data variables.product.prodname_dotcom %} 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 1adb41d31a..1a1dfbab80 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 @@ -29,7 +29,7 @@ Um executor auto-hospedado recebe automaticamente certas etiquetas ao ser adicio * `auto-hospedado`: Etiqueta-padrão aplicada a todos os executores auto-hospedados. * `Linux`, `Windows`, ou `macOS`: Aplicado, dependendo do sistema operacional. -* `x86`, `x64`, `ARM`, ou `ARM64`: Aplicado, dependendo da arquitetura do hardware. +* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. 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: diff --git a/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md index 5d4c1fe7e9..66b27db7c1 100644 --- a/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md @@ -41,12 +41,17 @@ As máquinas virtuais do Windows estão configuradas para ser executadas como ad ### Executores e recursos de hardware compatíveis -Cada máquina virtual tem os mesmos recursos de hardware disponíveis. +Hardware specification for Windows and Linux virtual machines: - CPU dual core - 7 GB de memória RAM - 14 GB de espaço de disco SSD +Hardware specification for macOS virtual machines: +- 3-core CPU +- 14 GB de memória RAM +- 14 GB de espaço de disco SSD + {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} @@ -71,9 +76,13 @@ As ferramentas do software incluídas em executores hospedados em {% data variab Executores hospedados no {% data variables.product.prodname_dotcom %} incluem as ferramentas integradas padrão do sistema operacional, além dos pacotes listados nas referências acima. Por exemplo, os executores do Ubuntu e do macOS incluem `grep`, `find` e `which`, entre outras ferramentas-padrão. -Os registros do fluxo de trabalho incluem um link para as ferramentas pré-instaladas no executor. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)". +Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will tell you the the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -Se houver uma ferramenta que você queira solicitar, abra um problema em [actions/virtual-environments](https://github.com/actions/virtual-environments). +We recommend using actions to interact with the software installed on runners. This approach has several benefits: +- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters +- It ensures the tool versions used in your workflow will remain the same regardless of software updates + +Se houver uma ferramenta que você queira solicitar, abra um problema em [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners. ### Endereços IP diff --git a/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index e0b46b7b9c..07e75ad51b 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -73,7 +73,7 @@ Se o servidor em que você está executando {% endif %} #### Habilitar a verificação de código para repositórios individuais -Depois que você configurar um executor auto-hospedado, {% if currentVersion == "enterprise-server@2.22" %}e provisionar as ações,{% endif %} os usuários poderão habilitar {% data variables.product.prodname_code_scanning %} para repositórios individuais em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning). +Depois que você configurar um executor auto-hospedado, {% if currentVersion == "enterprise-server@2.22" %}e provisionar as ações,{% endif %} os usuários poderão habilitar {% data variables.product.prodname_code_scanning %} para repositórios individuais em {% data variables.product.product_location %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." ### Executar {% data variables.product.prodname_code_scanning %} usando o {% data variables.product.prodname_codeql_runner %} Se você não quiser usar {% data variables.product.prodname_actions %}, você poderá executar {% data variables.product.prodname_code_scanning %} usando o {% data variables.product.prodname_codeql_runner %}. diff --git a/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index fa33e83cea..0b052a3413 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md @@ -20,7 +20,7 @@ Para criptografia em trânsito, {% data variables.product.product_name %} usa o A chave que você fornecer é armazenada em um módulo de segurança de hardware (HSM) em um cofre chave que {% data variables.product.company_short %} gerencia. -Para configurar sua chave de criptografia, use a API REST. Existem vários pontos de extremidade da API, por exemplo, para verificar o status da criptografia, atualizar sua chave de criptografia e excluir sua chave de criptografia. Observe que que apagar sua chave irá congelar a sua empresa. Para obter mais informações sobre os pontos de extremidade da API, consulte "[Criptografia estática](/rest/reference/enterprise-admin#encryption-at-rest)" na documentação da API REST. +Para configurar sua chave de criptografia, use a API REST. Existem vários pontos de extremidade da API, por exemplo, para verificar o status da criptografia, atualizar sua chave de criptografia e desabilitar sua chave de criptografia. Observe que que desabilitar a sua chave irá congelar a sua empresa. Para obter mais informações sobre os pontos de extremidade da API, consulte "[Criptografia estática](/rest/reference/enterprise-admin#encryption-at-rest)" na documentação da API REST. ### Adicionar ou atualizar uma chave de criptografia @@ -48,24 +48,24 @@ Sua chave privada RSA de 2048 bits deve estar no formato PEM como, por exemplo, curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` -### Excluir a sua chave de criptografia +### Desabilitar a sua chave de criptografia -Para congelar a sua empresa, por exemplo, no caso de uma violação, você pode desabilitar a criptografia, excluindo sua chave de criptografia. +Para congelar a sua empresa, por exemplo, no caso de uma violação, você pode desabilitar a criptografia, marcando a sua chave de criptografia como desabilitada. -Para descongelar a sua empresa depois de ter excluído sua chave de criptografia, entre em contato com o suporte. Para obter mais informações, consulte "[Sobre o {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)". - -1. Para excluir sua chave e desabilitar a criptografia estática, use o ponto de extremidade `DELETE /enterprise/encryption`. +1. Para desabilitar a sua chave e a criptografia estática, use o ponto de extremidade `DELETE /enterprise/encryption`. Esta operação não exclui a chave permanentemente. ```shell curl -X DELETE http(s)://hostname/api/v3/enterprise/encryption ``` -2. Opcionalmente, verifique o status da operação de exclusão. +2. Opcionalmente, verifique o status da operação de exclusão. Demora aproximadamente dez minutos para desabilitar a criptografia em repouso. ```shell curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` +Para descongelar a sua empresa depois de ter desabilitado a sua chave de criptografia, entre em contato com o suporte. Para obter mais informações, consulte "[Sobre o {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)". + ### Leia mais - "[Criptografia estática](/rest/reference/enterprise-admin#encryption-at-rest)" na documentação da API REST diff --git a/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md index 7e52b13a56..e3a1fe884c 100644 --- a/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -29,6 +29,26 @@ versions: {% endnote %} +{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %} + +### Sobre os requisitos mínimos para {% data variables.product.prodname_ghe_server %} 3.0 ou posterior + +Antes de atualizar para {% data variables.product.prodname_ghe_server %} 3.0 ou posterior, revise os recursos de hardware que você forneceu para sua instância. {% data variables.product.prodname_ghe_server %} 3.0 introduz novas funcionalidades, como {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %}, e exige mais recursos do que as versões 2.22 e anteriores. Para obter mais informações, consulte as observações sobre a versão [{% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/release-notes). + +Os requisitos aumentados para {% data variables.product.prodname_ghe_server %} 3.0 e posterior estão em **negrito** na tabela a seguir. + +| Licenças de usuário | vCPUs | Memória | Armazenamento anexado | Armazenamento raiz | +|:---------------------------------------- | -----------------------------:| -------------------------------------:| -------------------------------------:| ------------------:| +| Teste, demonstração ou 10 usuários leves | **4**
_Up from 2_ | **32 GB**
_Up de 16 GB_ | **150 GB**
_Up de 100 GB_ | 200 GB | +| 10-3000 | **8**
_Up de 4_ | **48 GB**
_Up de 32 GB_ | **300 GB**
_Up de 250 GB_ | 200 GB | +| 3000-5000 | **12**
_Up de 8_ | 64 GB | 500 GB | 200 GB | +| 5000-8000 | **16**
_Up de 12_ | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | **20**
_Up de 16_ | **160 GB**
_Up de 128 GB_ | 1000 GB | 200 GB | + +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% endif %} + ### Obter um instantâneo Instantâneo é um ponto de verificação de uma máquina virtual (VM) em um momento específico. É altamente recomendável obter um instantâneo antes de atualizar sua máquina virtual para que você possa recuperar a VM em caso de falha. Se você estiver atualizando para uma nova versão do recurso, obtenha um instantâneo da VM. Se você estiver atualizando para uma versão de patch, vincule o disco de dados existente. diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md index 155ef3b748..aca4dc713d 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -9,13 +9,7 @@ versions: enterprise-server: '>=2.22' --- -{% if currentVersion == "enterprise-server@2.22" %} -{% note %} - -**Observação:** O suporte de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22 é beta pública limitada. Revise os requisitos de armazenamento externo abaixo e [inescreva-se para a versão beta](https://resources.github.com/beta-signup/). - -{% endnote %} -{% endif %} +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} @@ -23,11 +17,33 @@ versions: Este artigo explica como os administradores do site podem configurar {% data variables.product.prodname_ghe_server %} para usar {% data variables.product.prodname_actions %}. Ele abrange os requisitos de hardware e software, apresenta as opções de armazenamento e descreve as políticas de gestão de segurança. +{% endif %} + ### Revise as considerações de hardware +{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %} + +{% note %} + +**Observação**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} estava disponível para {% data variables.product.prodname_ghe_server %} 2.22 como beta limitada. {% endif %}Se você estiver fazendo a atualização de uma instância de {% data variables.product.prodname_ghe_server %} existente para 3.0 ou posterior e desejar configurar {% data variables.product.prodname_actions %}, observe que os requisitos mínimos de hardware aumentaram. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)". + +{% endnote %} + +{% endif %} + {% data reusables.actions.enterprise-hardware-considerations %} -{% endif %} +Para obter mais informações sobre requisitos de recursos para {% data variables.product.prodname_ghe_server %}, consulte considerações de hardware para a plataforma da sua instância. + +- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) +- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) +- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) +- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) +- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) +- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations) +- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations) + +{% data reusables.enterprise_installation.about-adjusting-resources %} ### Requisitos de armazenamento externo @@ -55,7 +71,7 @@ O {% data variables.product.prodname_actions %} usa armazenamento do blob para a ### Habilitar {% data variables.product.prodname_actions %} -O suporte de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22 é beta pública limitada. [Inscreva-se para a versão beta](https://resources.github.com/beta-signup/). +O suporte de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22 estava disponível como uma versão beta limitada. Para configurar {% data variables.product.prodname_actions %} para sua instância, atualize para {% data variables.product.prodname_ghe_server %} 3.0 ou posterior. Para obter mais informações, consulte as observações da versão de [{% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/release-notes) e "[Atualizar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)". ### Leia mais diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md index f2da3718b9..7d675b5311 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md @@ -8,40 +8,40 @@ versions: free-pro-team: '*' --- -### Clonar repositórios -Os repositórios no {% data variables.product.prodname_dotcom %} existem como repositórios remotos. É possível clonar repositórios públicos pertencentes a outras pessoas. É possível clonar o seu próprio repositório para criar uma cópia loca* no seu computador e fazer a sincronia entre os dois locais. +### About local repositories +Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer. + +You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. Para obter mais informações, consulte "[Sincronizando seu branch](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)". + +When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. Para obter mais informações, consulte "[Sobre bifurcações](/github/collaborating-with-issues-and-pull-requests/about-forks)". + +When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)". Também é possível clonar um repositório diretamente no {% data variables.product.prodname_dotcom %} ou no {% data variables.product.prodname_enterprise %}. Para obter mais informações, consulte "[Clonar um repositório do {% data variables.product.prodname_dotcom %} para o {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)". -{% mac %} +### Clonar um repositório {% data reusables.desktop.choose-clone-repository %} - ![Opção de menu Clone (Clonar) no app Mac](/assets/images/help/desktop/clone-file-menu-mac.png) {% data reusables.desktop.cloning-location-tab %} - ![Guias Location (Local) no menu Clone a repository (Clonar um repositório)](/assets/images/help/desktop/choose-repository-location-mac.png) {% data reusables.desktop.cloning-repository-list %} - ![Clonar uma lista de repositórios](/assets/images/help/desktop/clone-a-repository-list-mac.png) -4. Clique em **Choose...** (Escolher...). Em seguida, navegue pela janela Finder (Localizador) até o local em que você pretende clonar o repositório. ![Botão Choose (Escolher)](/assets/images/help/desktop/clone-choose-button-mac.png) -5. Clique em **Clone** (Clonar). ![Botão Clone (Clonar)](/assets/images/help/desktop/clone-button-mac.png) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} -{% endmac %} - -{% windows %} +### Bifurcar um repositório +If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork. {% data reusables.desktop.choose-clone-repository %} - ![Opção de menu Clone (Clonar) no app Windows](/assets/images/help/desktop/clone-file-menu-windows.png) {% data reusables.desktop.cloning-location-tab %} - ![Guias Location (Local) no menu Clone a repository (Clonar um repositório)](/assets/images/help/desktop/choose-repository-location-win.png) {% data reusables.desktop.cloning-repository-list %} - ![Clonar uma lista de repositórios](/assets/images/help/desktop/clone-a-repository-list-win.png) -4. Clique em **Choose...** (Escolher...). Em seguida, navegue pelo Windows Explorer (Explorador do Windows) até o local em que você pretende clonar o repositório. ![Botão Choose (Escolher)](/assets/images/help/desktop/clone-choose-button-win.png) -5. Clique em **Clone** (Clonar). ![Botão Clone (Clonar)](/assets/images/help/desktop/clone-button-win.png) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} +{% data reusables.desktop.fork-type-prompt %} -{% endwindows %} +### Managing fork behavior +You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}. -### Bifurcar os repositórios -Para contribuir para um projeto em que você não tem acesso de gravação, você pode usar o {% data variables.product.prodname_desktop %} para criar uma bifurcação do repositório. As alterações na sua bifurcação não afetam o repositório original. Você pode fazer commit das alterações na sua bifurcação e, em seguida, abrir um pull request no repositório original com as alterações propostas. Para obter mais informações, consulte "[Sobre bifurcações](/github/collaborating-with-issues-and-pull-requests/about-forks)". +{% data reusables.desktop.open-repository-settings %} +{% data reusables.desktop.select-fork-behavior %} -1. Se você clonar um repositório em que você não tem acesso de gravação e tentar fazer commit das alterações, {% data variables.product.prodname_desktop %} informará que "você não tem acesso de gravação para o **REPOSITÓRIO**. Clique em **criar uma bifurcação**. ![Criar um link debifurcação](/assets/images/help/desktop/create-a-fork.png) -3. Clique em **Bifurcar este repositório**. ![Botão bifurcar este repositório](/assets/images/help/desktop/fork-this-repo-button.png) -4. Para visualizar a sua bifurcação no {% data variables.product.prodname_dotcom %}, no canto superior direito do {% data variables.product.prodname_dotcom %}, clique na imagem do seu perfil e, em seguida, clique em **Seus repositórios**. ![Seu link para repositórios](/assets/images/help/profile/your-repositories.png) +### Leia mais +- [Sobre repositórios remotos](/github/using-git/about-remote-repositories) diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 97af095f92..f0a8cc6774 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -9,7 +9,7 @@ versions: ### Sobre tags no {% data variables.product.prodname_desktop %} -O {% data variables.product.prodname_desktop %} permite que você crie tags anotadas. É possível usar uma tag para marcar um ponto individual no histórico do seu repositório, incluindo um número de versão para uma versão. Para obter mais informações sobre tags de versão, consulte "[Sobre versões](/github/administering-a-repository/about-releases)" +O {% data variables.product.prodname_desktop %} permite que você crie tags anotadas. As tags são associadas a commits. Portanto, você pode usar uma tag para marcar um ponto individual no histórico do seu repositório, incluindo um número de versão para uma versão. Para obter mais informações sobre tags de versão, consulte "[Sobre versões](/github/administering-a-repository/about-releases)" {% data reusables.desktop.tags-push-with-commits %} @@ -44,3 +44,7 @@ O {% data variables.product.prodname_desktop %} permite que você crie tags anot {% data reusables.desktop.history-tab %} {% data reusables.desktop.delete-tag %} + +### Leia mais + +- "[Princípios básicos do Git - Tags](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" na documentação do Git diff --git a/translations/pt-BR/content/developers/apps/activating-beta-features-for-apps.md b/translations/pt-BR/content/developers/apps/activating-beta-features-for-apps.md index 52d20e2c2f..50559a476e 100644 --- a/translations/pt-BR/content/developers/apps/activating-beta-features-for-apps.md +++ b/translations/pt-BR/content/developers/apps/activating-beta-features-for-apps.md @@ -3,6 +3,8 @@ title: Ativar recursos beta para os aplicativos intro: 'Você pode testar novos recursos dos aplicativos lançados em beta público para seus {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_app %}s.' versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% warning %} diff --git a/translations/pt-BR/content/developers/apps/authenticating-with-github-apps.md b/translations/pt-BR/content/developers/apps/authenticating-with-github-apps.md index 1b3f209e7a..c958458967 100644 --- a/translations/pt-BR/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/pt-BR/content/developers/apps/authenticating-with-github-apps.md @@ -109,8 +109,8 @@ O exemplo acima usa o tempo máximo de expiração de 10 minutos, após o qual a ```json { - "message": "'Expiration' claim ('exp') deve ser um valor numérico que representa o tempo futuro em que expira a declaração.", - "documentation_url": "{% data variables.product.doc_url_pre %}/v3" + "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 %}" } ``` diff --git a/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 7cd3cf5cf7..e574e71dc9 100644 --- a/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### Introdução -Este guia irá apresentá-lo aos [aplicativos Github](/apps/) e à [API de verificação](/rest/reference/checks), que você usará para criar um servidor de integração contínua (CI) que executa testes. +This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. A CI é uma prática de software que exige o commit do código em um repositório compartilhado. Fazer commits de códigos com frequência detecta erros com mais antecedência e reduz a quantidade de código necessária para depuração quando os desenvolvedores chegam à origem de um erro. As atualizações frequentes de código também facilitam o merge de alterações dos integrantes de uma equipe de desenvolvimento de software. Assim, os desenvolvedores podem se dedicar mais à gravação de códigos e se preocupar menos com erros de depuração ou conflitos de merge. 🙌 @@ -49,7 +49,7 @@ Para ter uma ideia do que seu servidor de CI da API de verificações fará quan ### Pré-requisitos -Antes de começar, é possível que você deseje familiarizar-se com os [aplicativos Github](/apps/), [Webhooks](/webhooks) e a [API de verificação](/rest/reference/checks), caso você ainda não esteja familiarizado. Você encontrará mais APIs na [documentação da API REST](/rest). A API de Verificações também está disponível para uso no [GraphQL](/graphql), mas este início rápido foca no REST. Consulte o GraphQL [Conjunto de verificações](/graphql/reference/objects#checksuite) e os objetos de [execução de verificação](/graphql/reference/objects#checkrun) objetos para obter mais informações. +Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. Você encontrará mais APIs na [documentação da API REST](/rest). A API de Verificações também está disponível para uso no [GraphQL](/graphql), mas este início rápido foca no REST. Consulte o GraphQL [Conjunto de verificações](/graphql/reference/objects#checksuite) e os objetos de [execução de verificação](/graphql/reference/objects#checkrun) objetos para obter mais informações. Você usará a [linguagem de programação Ruby](https://www.ruby-lang.org/en/), o serviço de entrega de da carga do webhook [Smee](https://smee.io/), a [biblioteca do Ruby Octokit.rb](http://octokit.github.io/octokit.rb/) para a API REST do GitHub e a [estrutura web Sinatra](http://sinatrarb.com/) para criar seu aplicativo do servidor de verificações de CI da API. @@ -203,7 +203,7 @@ Se você vir outros aplicativos na aba Verificações, isso significa que você ### Etapa 1.4. Atualizar a execução de verificação -Quando o seu método `create_check_run` é executado, ele pede ao GitHub para criar uma nova execução de verificação. Quando o Github terminar de criar a execução de verificação, você receberá o evento do webhook `check_run` com a ação `criada`. Esse evento é o sinal para começar a executar a verificação. +Quando o seu método `create_check_run` é executado, ele pede ao GitHub para criar uma nova execução de verificação. When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. Esse evento é o sinal para começar a executar a verificação. Você vai atualizar o manipulador do evento para procurar a ação `criada`. Enquanto você está atualizando o manipulador de eventos, você pode adicionar uma condição para a ação `ressolicitada`. Quando alguém executa novamente um único teste no GitHub clicando no botão "Reexecutar", o GitHub envia o evento da execução de verificação `ressolicitado` para o seu aplicativo. Quando a execução de uma verificação é `ressolicitada`, você irá iniciar todo o processo e criar uma nova execução de verificação. diff --git a/translations/pt-BR/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/pt-BR/content/developers/apps/migrating-oauth-apps-to-github-apps.md index 19f4bc35f4..e138916242 100644 --- a/translations/pt-BR/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/pt-BR/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -52,7 +52,7 @@ Os aplicativos GitHub usam [regras móveis para limites de taxa](/apps/building- #### Cadastre um novo aplicativo GitHub -Uma vez que você decidiu fazer a troca para os aplicativos GitHub, você precisará [criar um novo aplicativo GitHub](/apps/building-github-apps/). +Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). #### Determine as permissões de que seu aplicativo precisa @@ -62,7 +62,7 @@ Nas configurações do seu aplicativo GitHub, você pode especificar se seu apli #### Assine os webhooks -Após criar um novo aplicativo GitHub e selecionar suas permissões, você poderá selecionar os eventos do webhook que você deseja que ele assine. Consulte "[Editando as permissões do aplicativo Github](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" para aprender como se assinar webhooks. +Após criar um novo aplicativo GitHub e selecionar suas permissões, você poderá selecionar os eventos do webhook que você deseja que ele assine. See "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. #### Entenda os diferentes métodos de autenticação diff --git a/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md index 931a044d2d..9ed35fef6f 100644 --- a/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/pt-BR/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,7 +42,7 @@ Esta solicitação de retorno de chamada enviará um novo token de acesso e um n { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" diff --git a/translations/pt-BR/content/developers/apps/suspending-a-github-app-installation.md b/translations/pt-BR/content/developers/apps/suspending-a-github-app-installation.md index 9c2239cf5b..b1356a019b 100644 --- a/translations/pt-BR/content/developers/apps/suspending-a-github-app-installation.md +++ b/translations/pt-BR/content/developers/apps/suspending-a-github-app-installation.md @@ -5,6 +5,8 @@ redirect_from: - /apps/managing-github-apps/suspending-a-github-app-installation versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% note %} diff --git a/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index f8bad5dc24..4f99310da8 100644 --- a/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -14,7 +14,7 @@ versions: {% warning %} -Se você oferecer um aplicativo GitHub no {% data variables.product.prodname_marketplace %}, seu aplicativo deve identificar os usuários que seguem o fluxo de autorização do OAuth. Você não precisa configurar um aplicativo OAuth separado para ser compatível com este fluxo. Consulte "[Identificando e autorizando usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obter mais informações. +If you offer a {% data variables.product.prodname_github_app %} in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate {% data variables.product.prodname_oauth_app %} to support this flow. See "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endwarning %} @@ -24,7 +24,7 @@ Antes de um cliente comprar o seu aplicativo no {% data variables.product.prodna O cliente efetua a compra clicando em **Concluir pedido e começar a instalação**. -O GitHub envia a o webhook de [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) com a ação `comprado` para o seu aplicativo. +{% data variables.product.product_name %} then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. Leia o objeto `effective_date` e `marketplace_purchase` do webhook `marketplace_purchase` para determinar qual plano o cliente comprou, quando começa o ciclo de cobrança, e quando começa o próximo ciclo de cobrança. @@ -34,27 +34,27 @@ Consulte "[ eventos de webhook de {% data variables.product.prodname_marketplace ### Etapa 2. Instalação -Se o seu aplicativo for um aplicativo GitHub, este pede ao cliente que selecione quais repositórios o aplicativo poderá acessar ao comprá-lo. Em seguida, o GitHub instala o aplicativo na conta selecionada pelo cliente e dá acesso aos repositórios selecionados. +If your app is a {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} prompts the customer to select which repositories the app can access when they purchase it. {% data variables.product.product_name %} then installs the app on the account the customer selected and grants access to the selected repositories. -Neste ponto, se você especificou uma **URL de configuração** nas suas configurações do aplicativo GitHub, o Github irá redirecionar o cliente para essa URL. Se você não especificar uma URL de configuração, você não poderá gerenciar as compras do seu aplicativo GitHub. +At this point, if you specified a **Setup URL** in your {% data variables.product.prodname_github_app %} settings, {% data variables.product.product_name %} will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your {% data variables.product.prodname_github_app %}. {% note %} -**Observação:** A **configuração da URL** é descrita como opcional nas configurações do aplicativo GitHub, mas é um campo obrigatório se você quiser oferecer seu aplicativo no {% data variables.product.prodname_marketplace %}. +**Note:** The **Setup URL** is described as optional in {% data variables.product.prodname_github_app %} settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. {% endnote %} -Se o seu aplicativo for um aplicativo OAuth, o GitHub não irá instalá-lo em lugar nenhum. Em vez disso, o GitHub redireciona o cliente para a **URL de Instalação** que você especificou na sua [listagem de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). +If your app is an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} does not install it anywhere. Instead, {% data variables.product.product_name %} redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). -Quando um cliente compra um aplicativo OAuth, o GitHub redireciona o cliente para a URL que você escolher (URL de configuração ou URL de instalação) e a URL inclui o plano de preços selecionado pelo cliente como um parâmetro de consulta: `marketplace_listing_plan_id`. +When a customer purchases an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. ### Etapa 3. Autorização Quando um cliente compra seu aplicativo, você deve enviar o cliente por meio do fluxo de autorização OAuth: -* Se seu aplicativo for um aplicativo GitHub, inicie o fluxo de autorização assim que o GitHub redirecionar o cliente para a **URL de configuração**. Siga os passos descritos em "[Identificando e autorizando usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". +* If your app is a {% data variables.product.prodname_github_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -* Se seu aplicativo for um aplicativo OAuth, inicie o fluxo de autorização assim que o GitHub redirecionar o cliente para a **URL de Instalação**. Siga as etapas em "[Autorizando aplicativos OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/)". +* If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)." Para qualquer tipo de aplicativo, o primeiro passo é redirecionar o cliente para https://github.com/login/oauth/authorize. diff --git a/translations/pt-BR/content/discussions/quickstart.md b/translations/pt-BR/content/discussions/quickstart.md index bf873d796f..6621eee184 100644 --- a/translations/pt-BR/content/discussions/quickstart.md +++ b/translations/pt-BR/content/discussions/quickstart.md @@ -24,7 +24,7 @@ Ao habilitar primeiro um {% data variables.product.prodname_discussions %}, voc 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**. ![Configure um botão de discussão em "Recursos" para habilitar ou desabilitar discussões 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. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) +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 diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md index 2a9fef23f6..253c4a285b 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -16,7 +16,7 @@ Repl.it é um ambiente de desenvolvimento integrado on-line (IDE) compatível co A primeira vez que o aluno clica no botão para acessar o Repl.it, o aluno deverá efetuar o login em Repl.it com as credenciais de {% data variables.product.product_name %}. Após efetuar o login, o aluno terá acesso a um ambiente de desenvolvimento que contém o código do repositório de atividades, totalmente configurado no Repl.it. -Para obter mais informações sobre como trabalhar no Repl.it, consulte o [Guia de início rápido do Repl.it](https://docs.repl.it/misc/quick-start#the-repl-environment). +Para obter mais informações sobre como trabalhar no Repl.it, consulte o [Guia de início rápido do Repl.it](https://docs.repl.it/repls/quick-start#the-repl-environment). Em atividades em grupo, os alunos podem usar o Repl.it Multiplayer para trabalhar de forma colaborativa. Para obter mais informações, consulte o site [Repl.it Multiplayer](https://repl.it/site/multiplayer). diff --git a/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md index d18d0ff406..4476000566 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -3,6 +3,7 @@ title: Sobre as atualizações da versão do Dependabot intro: 'Você pode usar o {% data variables.product.prodname_dependabot %} para manter os pacotes que usa atualizados para as versões mais recentes.' redirect_from: - /github/administering-a-repository/about-dependabot + - /github/administering-a-repository/about-github-dependabot - /github/administering-a-repository/about-github-dependabot-version-updates versions: free-pro-team: '*' @@ -14,7 +15,7 @@ versions: O {% data variables.product.prodname_dependabot %} facilita a manutenção de suas dependências. Você pode usá-lo para garantir que seu repositório se mantenha atualizado automaticamente com as versões mais recentes dos pacotes e aplicações do qual ele depende. -Você habilita o {% data variables.product.prodname_dependabot_version_updates %} verificando um arquivo de configuração no seu repositório. O arquivo de configuração especifica a localização do manifesto ou outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário. +Você habilita o {% data variables.product.prodname_dependabot_version_updates %} verificando um arquivo de configuração no seu repositório. O arquivo de configuração especifica a localização do manifesto ou de outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário. Quando {% data variables.product.prodname_dependabot %} identifica uma dependência desatualizada, ele cria uma pull request para atualizar o manifesto para a última versão da dependência. Para dependências de vendor, {% data variables.product.prodname_dependabot %} levanta um pull request para substituir diretamente a dependência desatualizada pela nova versão. Você verifica se os seus testes passam, revisa o changelog e lança observações incluídas no resumo do pull request e, em seguida, faz a mesclagem. Para obter detalhes, consulte "[Habilitando e desabilitando atualizações da versão](/github/administering-a-repository/enabling-and-disabling-version-updates)." diff --git a/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md index f9637a4993..f855043735 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-securing-your-repository.md @@ -14,6 +14,8 @@ O primeiro passo para proteger um repositório é configurar quem pode ver e mod {% data variables.product.prodname_dotcom %} tem um conjunto crescente de recursos de segurança que ajudam você a manter seu código protegido. Você pode encontrá-los na aba **Segurança** do seu repositório. +#### Available for all repositories + {% if currentVersion == "free-pro-team@latest" %} - **Política de segurança** @@ -43,15 +45,23 @@ Use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %} + +These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} + - **Alertas de {% data variables.product.prodname_code_scanning_capc %}** Detectar automaticamente vulnerabilidades de segurança e erros de codificação em códigos novos ou modificados. São destacados os problemas potenciais, com informações detalhadas, o que permite que você corrija o código antes que seja mesclado no seu branch-padrão. Para obter mais informações, consulte "[Sobre a varredura de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". - **Segredos detectados** -Visualizar qualquer segredo que - {% data variables.product.prodname_dotcom %} encontrou no seu código. Você deve tratar os tokens ou credenciais verificados no repositório como comprometidos. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." - {% endif %} + {% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else if %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. Você deve tratar os tokens ou credenciais verificados no repositório como comprometidos. Para obter mais informações, consulte "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +- **Revisão de dependências** - Mostra o impacto total das alterações nas dependências e vê detalhes de qualquer versão vulnerável antes de realizar o merge de um pull request. Para obter mais informações, consulte "[Revisar as mudanças de dependências em um pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". +{% endif %} ### Explorar dependências O gráfico de dependências de {% data variables.product.prodname_dotcom %} permite que você explore: @@ -59,6 +69,6 @@ O gráfico de dependências de {% data variables.product.prodname_dotcom %} perm * Ecossistemas e pacotes dos quais o repositório depende * Repositórios e pacotes que dependem do seu repositório -Você deve habilitar o gráfico de dependências antes de {% data variables.product.prodname_dotcom %} pode gerar {% data variables.product.prodname_dependabot_alerts %} para dependências com vulnerabilidades de segurança. +Você deve habilitar o gráfico de dependências antes de {% data variables.product.prodname_dotcom %} pode gerar {% data variables.product.prodname_dependabot_alerts %} para dependências com vulnerabilidades de segurança. {% if currentVersion == "free-pro-team@latest" %}Enabling the dependency graph also enables {% data variables.product.prodname_dotcom %} to run dependency reviews of pull requests.{% endif %} Você pode encontrar o gráfico de dependências na aba **Ideias** para o seu repositório. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". diff --git a/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md index 7441c35eb9..586de7e0b0 100644 --- a/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md +++ b/translations/pt-BR/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -27,13 +27,13 @@ versions: {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 4. Se "{% data variables.product.prodname_secret_scanning_caps %}" não for exibido na página, você deverá habilitar {% data variables.product.prodname_GH_advanced_security %} primeiro. À direita de "{% data variables.product.prodname_GH_advanced_security %}", clique em **Habilitar**. ![Habilitar {% data variables.product.prodname_GH_advanced_security %} para o seu repositório](/assets/images/help/repository/enable-ghas-dotcom.png) 5. Clique **Habilitar {% data variables.product.prodname_GH_advanced_security %} para este repositório** para confirmar a ação. ![Confirme a habilitação de {% data variables.product.prodname_GH_advanced_security %} para o seu repositório](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) 6. Quando você habilitar {% data variables.product.prodname_GH_advanced_security %} isto poderá habilitar automaticamente {% data variables.product.prodname_secret_scanning %} para o repositório (este é controlado pela configuração da organização). Se "{% data variables.product.prodname_secret_scanning_caps %}" é exibido com um botão **habilitar**. Você ainda precisa habilitar {% data variables.product.prodname_secret_scanning %} clicando em **Habilitar**. Se você vir um botão **Desabilitar**, significa que {% data variables.product.prodname_secret_scanning %} já está habilitado. - ![Habilitar {% data variables.product.prodname_secret_scanning %} para o seu repositório](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Habilitar {% data variables.product.prodname_secret_scanning %} para o seu repositório](/assets/images/help/repository/enable-secret-scanning-dotcom.png) + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} 4. À direita de " {% data variables.product.prodname_secret_scanning_caps %}", clique em **Habilitar**. ![Habilitar {% data variables.product.prodname_secret_scanning %} para o seu repositório](/assets/images/help/repository/enable-secret-scanning-ghe.png) diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index 7aa3dbe16b..c5e7a9a013 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -4,13 +4,12 @@ intro: "Você pode permitir ou impedir um merge automático de pull requests em product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' permissions: Pessoas com permissões de mantenedor podem gerenciar merge automático para pull requests em um repositório. --- -{% data reusables.pull_requests.auto-merge-release-phase %} - Se você permitir um merge automático para pull requests no seu repositório, as pessoas podem configurar os pull requests individuais no repositório para fazer merge automaticamente quando todos os requisitos de merge forem atendidos. Para obter mais informações, consulte "[Fazer merge automático de um pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Em "Botão de merge", selecione ou desmarque a opção **Permitir merge automático**. ![Caixa de seleção para permitir ou impedir merge automático](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) \ No newline at end of file +1. Em "Botão de merge", selecione ou desmarque a opção **Permitir merge automático**. ![Caixa de seleção para permitir ou impedir merge automático](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) diff --git a/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index 066ce1fb66..68ae41d678 100644 --- a/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -33,10 +33,15 @@ Você pode gerenciar os recursos de segurança e análise do repositório {% if {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} 4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. -{% if currentVersion == "free-pro-team@latest" %}Se "{% data variables.product.prodname_secret_scanning_caps %}" não for exibido, talvez seja necessário habilitar {% data variables.product.prodname_GH_advanced_security %} primeiro. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} +**Note:** If you disable + + {% data variables.product.prodname_GH_advanced_security %}, both {% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail. + {% endnote %} + + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} ![Botão "Habilitar" ou "Desabilitar" para "Configurar recursos de segurança e análise" ](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) {% endif %} diff --git a/translations/pt-BR/content/github/administering-a-repository/securing-your-repository.md b/translations/pt-BR/content/github/administering-a-repository/securing-your-repository.md index ad26bac52d..82e39209a4 100644 --- a/translations/pt-BR/content/github/administering-a-repository/securing-your-repository.md +++ b/translations/pt-BR/content/github/administering-a-repository/securing-your-repository.md @@ -6,5 +6,6 @@ redirect_from: - /articles/securing-your-repository versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- diff --git a/translations/pt-BR/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/pt-BR/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md index c8cb73b3f6..63a76e7860 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md +++ b/translations/pt-BR/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md @@ -33,14 +33,18 @@ Se você estiver usando uma chave GPG que corresponda à identidade do committer Comment: GitHub key Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? ``` -7. Digite `O` para salvar as seleções. +7. Insira `O` para confirmar suas seleções. 8. Insira a frase secreta da sua chave. -9. Digite `gpg --armor --export GPG key ID`, substituindo a ID da chave GPG que deseja usar. No seguinte exemplo, a ID da chave GPG é `3AA5C34371567BD2`: +9. Enter `gpg> save` to save the changes + ```shell + $ gpg> save + ``` +10. Digite `gpg --armor --export GPG key ID`, substituindo a ID da chave GPG que deseja usar. No seguinte exemplo, a ID da chave GPG é `3AA5C34371567BD2`: ```shell $ gpg --armor --export 3AA5C34371567BD2 # Prints the GPG key, in ASCII armor format ``` -10. Faça upload da chave GPG [adicionando-a à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). +11. Faça upload da chave GPG [adicionando-a à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). ### Leia mais diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index 8da18bc914..bca00eac72 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -4,10 +4,9 @@ intro: 'Você pode aumentar a velocidade de desenvolvimento permitindo o merge a product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' --- -{% data reusables.pull_requests.auto-merge-release-phase %} - ### Sobre o merge automático Se você habilitar o merge automático para um pull request, este será mesclado automaticamente quando todas as revisões necessárias forem atendidas e as verificações de status forem aprovadas. O merge automático impede que você espere que os sejam atendidos para que você possa passar para outras tarefas. diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md index 667ec3cc87..4f82c26359 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md @@ -1,6 +1,6 @@ --- -title: Criar uma pull request -intro: 'Crie uma 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.' +title: Criar um 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.' redirect_from: - /articles/creating-a-pull-request versions: @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -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 sua 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)". +Qualquer pessoa com permissões de leitura em um repositório pode criar um 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)". É 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. diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index c5dd9cb1fc..bea81a7b69 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -9,7 +9,6 @@ versions: github-ae: '*' --- - ### Sobre merges de pull request Em uma pull request, você propõe que as alterações feitas em um branch head sejam mescladas em um branch base. Por padrão, qualquer pull request pode sofrer merge a qualquer momento, a menos que o branch head esteja em conflito com o branch base. No entanto, pode haver restrições sobre quando você puder fazer merge de um pull request em um branch específico. Por exemplo, você só pode fazer merge de um pull request no branch-padrão se as verificações de status necessárias forem aprovadas. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)". diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index 163aaade01..202e14661d 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -23,7 +23,7 @@ Quando alguém com permissões de administrador ou proprietário tiver habilitad {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2. 9" %}Se uma equipe habilitou as atribuições de revisão de código, as aprovações individuais não vão atender ao requisito para a aprovação do proprietário do código em um branch protegido. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Se um arquivo tiver um proprietário do código, você poderá ver quem é o proprietário do código antes de abrir um pull request. No repositório, é possível pesquisar o arquivo e passar o mouse sobre {% octicon "shield-lock" aria-label="The edit icon" %}. diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 57094f656f..874a5f6be0 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -134,19 +134,22 @@ Tenta construir o código para as linguagens compiladas C/C++, C# e Java. Para e Analisa o código nos bancos de dados do {% data variables.product.prodname_codeql %} e faz o upload dos resultados para o {% data variables.product.product_location %}. -| Sinalizador | Obrigatório | Valor de entrada | -| -------------------------------- |:-----------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--repository` | ✓ | Nome do repositório a ser analisado. | -| `--commit` | ✓ | SHA do commit a ser analisado. No Git e no Azure DevOps, isso corresponde ao valor de `git rev-parse HEAD`. No Jenkins, isso corresponde a `$GIT_COMMIT`. | -| `--ref` | ✓ | Nome da referência para análise, por exemplo `refs/heads/main`. No Git e no Jenkins, isso corresponde ao valor de `git simbolic-ref HEAD`. No Azure DevOps, isso corresponde a `$(Build.SourceBranch)`. | -| `--github-url` | ✓ | URL da instância do {% data variables.product.prodname_dotcom %} onde seu repositório está hospedado. | -| `--github-auth` | ✓ | Um token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal. | -| `--checkout-path` | | O caminho para o checkout do seu repositório. O padrão é o diretório de trabalho atual. | -| `--no-upload` | | Nenhum. Impede que o {% data variables.product.prodname_codeql_runner %} faça o upload dos resultados para {% data variables.product.product_location %}. | -| `--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. | -| `--temp-dir` | | Diretório onde os arquivos temporários são armazenados. O padrão é _./codeql-runner_. | -| `--debug` | | Nenhum. Imprime mais resultados verbose. | -| `-h`, `--help` | | Nenhum. Exibe ajuda para o comando. | +| Sinalizador | Obrigatório | Valor de entrada | +| ---------------------------------- |:-----------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `--repository` | ✓ | Nome do repositório a ser analisado. | +| `--commit` | ✓ | SHA do commit a ser analisado. No Git e no Azure DevOps, isso corresponde ao valor de `git rev-parse HEAD`. No Jenkins, isso corresponde a `$GIT_COMMIT`. | +| `--ref` | ✓ | Nome da referência para análise, por exemplo `refs/heads/main`. No Git e no Jenkins, isso corresponde ao valor de `git simbolic-ref HEAD`. No Azure DevOps, isso corresponde a `$(Build.SourceBranch)`. | +| `--github-url` | ✓ | URL da instância do {% data variables.product.prodname_dotcom %} onde seu repositório está hospedado. | +| `--github-auth` | ✓ | Um token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal. | +| `--checkout-path` | | O caminho para o checkout do seu repositório. O padrão é o diretório de trabalho atual. | +| `--no-upload` | | Nenhum. Impede que o {% data variables.product.prodname_codeql_runner %} faça o upload dos resultados para {% data variables.product.product_location %}. | +| `--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. Excludes code snippets from the SARIF output. | +| `--threads` | | Número de threads a serem usados ao executar consultas. O padrão é usar todos os núcleos disponíveis. | +| `--temp-dir` | | Diretório onde os arquivos temporários são armazenados. O padrão é _./codeql-runner_. | +| `--debug` | | Nenhum. Imprime mais resultados verbose. | +| `-h`, `--help` | | Nenhum. Exibe ajuda para o comando. | #### `fazer upload` diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md index 62eccbbbb5..575a896856 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md @@ -17,7 +17,7 @@ versions: ### Sobre o {% data variables.product.prodname_codeql_workflow %} e linguagens compiladas -Para habilitar o {% data variables.product.prodname_code_scanning %} para seu repositório, você deve adicionar ao repositório um fluxo de trabalho do {% data variables.product.prodname_actions %} que inclui análise do {% data variables.product.prodname_codeql %}. Para {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, você adiciona o {% data variables.product.prodname_codeql_workflow %}. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning). +You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. Para {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, você adiciona o {% data variables.product.prodname_codeql_workflow %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} Para informações gerais sobre configuração diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md index 15e5332649..aba2368a4a 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md @@ -14,7 +14,7 @@ versions: {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %} {% link_in_list /about-code-scanning %} {% link_in_list /triaging-code-scanning-alerts-in-pull-requests %} - {% link_in_list /enabling-code-scanning %} + {% link_in_list /setting-up-code-scanning-for-a-repository %} {% link_in_list /managing-code-scanning-alerts-for-your-repository %} {% link_in_list /configuring-code-scanning %} {% link_in_list /configuring-the-codeql-workflow-for-compiled-languages %} diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 7a1747e907..1e5a825121 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -16,7 +16,7 @@ redirect_from: ### Sobre os alertas de {% data variables.product.prodname_code_scanning %} -Você pode configurar {% data variables.product.prodname_code_scanning %} para verificar o código em um repositório usando a análise-padrão de {% data variables.product.prodname_codeql %}, uma análise de terceiros ou vários tipos de análise. Quando a análise for concluída, os alertas resultantes serão exibidos lado a lado na visualização de segurança do repositório. Os resultados de ferramentas de terceiros ou de consultas personalizadas podem não incluir todas as propriedades que você vê para alertas detectados pela análise-padrão {% data variables.product.prodname_codeql %} de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Habilitando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning). +Você pode configurar {% data variables.product.prodname_code_scanning %} para verificar o código em um repositório usando a análise-padrão de {% data variables.product.prodname_codeql %}, uma análise de terceiros ou vários tipos de análise. Quando a análise for concluída, os alertas resultantes serão exibidos lado a lado na visualização de segurança do repositório. Os resultados de ferramentas de terceiros ou de consultas personalizadas podem não incluir todas as propriedades que você vê para alertas detectados pela análise-padrão {% data variables.product.prodname_codeql %} de {% data variables.product.company_short %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." Por padrão, {% data variables.product.prodname_code_scanning %} analisa seu código periodicamente no branch-padrão e durante os pull requests. Para obter informações sobre o gerenciamento de alertas em um pull request, consulte "[Triar aletras de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". @@ -28,7 +28,7 @@ Cada alerta destaca um problema com o código e o nome da ferramenta que o ident ![Exemplo de alerta de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) -Se você habilitar o {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_codeql %}, isso também poderá detectar problemas no fluxo de dados no seu código. A análise do fluxo de dados encontra potenciais problemas de segurança no código, tais como: usar dados de forma insegura, passar argumentos perigosos para funções e vazar informações confidenciais. +If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. A análise do fluxo de dados encontra potenciais problemas de segurança no código, tais como: usar dados de forma insegura, passar argumentos perigosos para funções e vazar informações confidenciais. 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. @@ -65,7 +65,7 @@ Fechar um alerta é uma maneira de resolver um alerta que você considera que n ### Ignorar ou excluir alertas -Há duas formas de fechar um alerta. Você pode corrigir o problema no código ou pode ignorar o alerta. Como alternativa, se você tiver permissões de administrador para o repositório, será possível excluir alertas. Excluir alertas é útil em situações em que você habilitou uma ferramenta {% data variables.product.prodname_code_scanning %} e, em seguida, decidiu removê-la ou em situações em que você habilitou a análise de {% data variables.product.prodname_codeql %} com um conjunto de consultas maior do que você deseja continuar usando, e, em seguida, você removeu algumas consultas da ferramenta. Em ambos os casos, excluir alertas permite limpar os seus resultados de {% data variables.product.prodname_code_scanning %}. Você pode excluir alertas da lista de resumo dentro da aba **Segurança**. +Há duas formas de fechar um alerta. Você pode corrigir o problema no código ou pode ignorar o alerta. Como alternativa, se você tiver permissões de administrador para o repositório, será possível excluir alertas. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. Em ambos os casos, excluir alertas permite limpar os seus resultados de {% data variables.product.prodname_code_scanning %}. Você pode excluir alertas da lista de resumo dentro da aba **Segurança**. Ignorar um alerta é uma maneira de fechar um alerta que você considera que não precisa ser corrigido. {% data reusables.code-scanning.close-alert-examples %} Você pode ignorar alertas de anotações de {% data variables.product.prodname_code_scanning %} no código ou da lista de resumo dentro na aba **Segurança**. @@ -127,5 +127,5 @@ Se um projeto tem vários alertas que você deseja ignorar pelo mesmo motivo, vo ### Leia mais - "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)" -- "[Habilitar {% data variables.product.prodname_code_scanning %} para um repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)" +- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" - "[Sobre a integração com {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)" diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 8f302d1359..b8a3532d26 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -24,7 +24,7 @@ Se você usar um sistema de integração contínua ou de entrega/implantação c {% data reusables.code-scanning.about-code-scanning %} Para obter informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning). -Você pode usar {% data variables.product.prodname_codeql_runner %} 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. Como alternativa, você pode usar {% data variables.product.prodname_actions %} para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_location %}. Para obter informações, consulte "[Habilitar {% data variables.product.prodname_code_scanning %} para um repositório](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)". +Você pode usar {% data variables.product.prodname_codeql_runner %} 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. Como alternativa, você pode usar {% data variables.product.prodname_actions %} para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_location %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." O {% data variables.product.prodname_codeql_runner %} é uma ferramenta de linha de comando que executa a análise de {% data variables.product.prodname_codeql %} em um checkout de um repositório do {% data variables.product.prodname_dotcom %}. Você adiciona o executor ao seu sistema de terceiros e, em seguida, chama o executor para analisar o código e fazer o upload dos resultados para o {% data variables.product.product_location %}. Estes resultados são exibidos como alertas do {% data variables.product.prodname_code_scanning %} no repositório. diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 7a4bc1a77d..e5e8593b7d 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -97,7 +97,6 @@ O {% data variables.product.prodname_code_scanning_capc %} usa o objeto `executa | `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). | -| `suppressions[].state` | **Opcional.** Quando o `estado` for definido como `aceito`, {% data variables.product.prodname_code_scanning %} irá atualizar o estado do resultado para `Fechado` em {% data variables.product.prodname_dotcom %}. | #### Objeto `local` diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md new file mode 100644 index 0000000000..e7af91fdd0 --- /dev/null +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -0,0 +1,117 @@ +--- +title: Setting up code scanning for a repository +shortTitle: Setting up code scanning +intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.' +redirect_from: + - /github/managing-security-vulnerabilities/configuring-automated-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} + +### Options for setting up {% data variables.product.prodname_code_scanning %} + +You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to use, at a repository level. O {% data variables.product.product_name %} fornece suporte totalmente integrado para a análise do {% data variables.product.prodname_codeql %} e também é compatível com ferramentas de análise usando ferramentas de terceiros. Para obter mais informações, consulte "[Sobre {% 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 %} + +### Setting up {% data variables.product.prodname_code_scanning %} using actions + +{% if currentVersion == "free-pro-team@latest" %}Usar ações para executar {% data variables.product.prodname_code_scanning %} levará minutos. Para obter mais informações, consulte "[Sobre a cobrança do {% 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. À direita de "{% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/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 %} ![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. ![Botão "Configurar este fluxo de trabalho" em "Começar com cabeçalho de {% data variables.product.prodname_code_scanning %}"](/assets/images/help/repository/code-scanning-set-up-this-workflow.png) +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. + + Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." +6. Use o menu suspenso **Iniciar commit** e digite uma mensagem de commit. ![Iniciar commit](/assets/images/help/repository/start-commit-commit-new-file.png) +7. Escolha se você gostaria de fazer commit diretamente no branch-padrão ou criar um novo branch e iniciar um pull request. ![Escolher onde fazer commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png) +8. Clique em **Fazer commit do novo arquivo** ou **Propor novo arquivo**. + +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. + +### 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. Para obter um exemplo de um script que apresenta pull requests para adicionar um fluxo de trabalho de {% data variables.product.prodname_actions %} em vários repositórios, veja o repositório [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs). + +### Visualizar a saída do registro de {% 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 %} + + 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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 %}. + + ![Clique no link "n alertas encontrados"](/assets/images/help/repository/code-scanning-alerts-found-link.png) + +{% endnote %} + +### Entendendo as verificações de pull request + +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. Há uma entrada para cada um dos trabalhos de análise no fluxo de trabalho e uma entrada final para os resultados da análise. + +Os nomes das verificações de análise de {% data variables.product.prodname_code_scanning %} assumem a forma: "TOOL NAME / JOB NAME (TRIGGER)." Por exemplo, para {% data variables.product.prodname_codeql %}, a análise do código C++ tem a entrada "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." Você pode clicar em **Detalhes** em uma entrada de análise de {% data variables.product.prodname_code_scanning %} para ver os dados de registro. Isso permite que você corrija um problema caso ocorra uma falha no trabalho de análise. Por exemplo, para a análise de {% data variables.product.prodname_code_scanning %} de linguagens compiladas, isto pode acontecer se a ação não puder criar o código. + + ![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". + + ![Análise ausente para mensagem de commit](/assets/images/help/repository/code-scanning-missing-analysis.png) + +#### Motivos da mensagem "faltando ausente" + +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". + +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: + +* O pull request foi levantado contra um branch diferente do branch padrão, e este branch não foi analisado. + + 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. + + ![Escolha um branch no menu suspenso Branch](/assets/images/help/repository/code-scanning-branch-dropdown.png) + + A solução nesta situação é adicionar o nome do branch de base para a especificação `on:push` e `on:pull_request` no fluxo de trabalho de {% data variables.product.prodname_code_scanning %} nesse branch e, em seguida, fazer uma alteração que atualize o pull request aberto que você deseja escanear. + +* O último commit no branch de base para o pull request está atualmente sendo analisado e a análise ainda não está disponível. + + Aguarde alguns minutos e depois faça push de uma alteração no pull request para acionar o recurso de {% data variables.product.prodname_code_scanning %}. + +* Ocorreu um erro ao analisar o último commit no branch base e a análise para esse commit não está disponível. + + Faça merge uma mudança trivial no branch de base para acionar {% data variables.product.prodname_code_scanning %} neste commit mais recente e, em seguida, faça push de uma alteração para o pull request reiniciar {% data variables.product.prodname_code_scanning %}. + +### Próximas etapas + +After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: + +- Visualizar todos os alertas de {% data variables.product.prodname_code_scanning %} gerados para este repositório. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/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 set up {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)". +- Configurar notificações para execuções concluídas. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)". +- Investigue todos os problemas que ocorrerem com a configuração inicial de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte "[Solucionar problemas no fluxo de trabalho de {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)". +- Personalize como {% data variables.product.prodname_code_scanning %} faz a varredura de código no seu repositório. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index d10a87bf69..8bcb31d730 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -15,7 +15,7 @@ versions: 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)". -Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com uma gravidade de `erro`, ocorre uma falha na verificação e o erro é relatado nos resultados de verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas são tratados como avisos ou notas e a verificação é considerada bem-sucedida. Se seu pull request tem como alvo um branch protegido que foi habilitado por {% data variables.product.prodname_code_scanning %}, e o proprietário do repositório configurou as verificações de status obrigatórias, você deverá corrigir ou {% if currentVersion == "enterprise-server@2. 2" %}fechar{% else %}dismiss{% endif %} todos os erros alertas antes que o pull request possa ser mesclado. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". +Se {% data variables.product.prodname_code_scanning %} tiver algum resultado com uma gravidade de `erro`, ocorre uma falha na verificação e o erro é relatado nos resultados de verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas são tratados como avisos ou notas e a verificação é considerada bem-sucedida. 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 you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". ![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) diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md index 2654037db9..00ca0f80bd 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -24,7 +24,7 @@ O nível de gravidade é um dos quatro níveis possíveis definidos no [Sistema - Alto - Crítico -O {% data variables.product.prodname_advisory_database %} usa padrões a versão 3.0 do CVSS e os níveis de CVSS descritos acima. {% data variables.product.product_name %} não publica pontuações de CVSS. +O {% data variables.product.prodname_advisory_database %} usa padrões a versão 3.0 do CVSS e os níveis de CVSS descritos acima. {% data reusables.repositories.github-security-lab %} @@ -41,24 +41,39 @@ O banco de dados também pode ser acessado usando a API do GraphQL. Para obter m {% endnote %} ### Pesquisar em {% data variables.product.prodname_advisory_database %} -Você pode pesquisar no banco de dados e usar qualificadores para restringir sua pesquisa com consultorias criadas em uma determinada data, em um ecossistema específico ou em uma biblioteca específica. + +Você pode procurar no banco de dados e usar qualificadores para limitar sua busca. Por exemplo, você pode procurar consultorias criadas em uma determinada data, em um ecossistema específico ou em uma biblioteca em particular. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Exemplo | -| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) mostrará apenas as consultorias que afetam os pacotes NPM. | -| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) mostrará apenas as consultorias com um alto nível de gravidade. | -| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) mostrará apenas as consultorias que afetam a biblioteca de lodash. | -| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) classificará os resultados, mostrando as consultorias mais antigas primeiro. | -| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) classificará os resultados mostrando as consultorias mais novas primeiro. | -| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) classificará os resultados, mostrando os menos atualizados primeiro. | -| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) classificará os resultados, mostrando os mais atualizados primeiro. | -| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) mostrará apenas as consultorias que foram retiradas. | -| `created:YYYY-MM-DD` | [**created:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2019-10-31) mostrará apenas as consultorias criadas nessa data. | -| `updated:YYYY-MM-DD` | [**updated:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2019-10-31) mostrará somente as consultorias atualizadas nesta data. | +| Qualifier | Exemplo | +| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `GHSA-ID` | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) mostrará a consultoria com o ID de {% data variables.product.prodname_advisory_database %}. | +| `CVE-ID` | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) mostrará a consultoria com este ID de CVE. | +| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) mostrará apenas as consultorias que afetam os pacotes NPM. | +| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) mostrará apenas as consultorias com um alto nível de gravidade. | +| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) mostrará apenas as consultorias que afetam a biblioteca de lodash. | +| `cwe:ID` | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) mostrará apenas as consultorias com este número de CWE. | +| `credit:USERNAME` | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) mostrará apenas as consultorias creditadas na conta de usuário "octocat". | +| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) classificará os resultados, mostrando as consultorias mais antigas primeiro. | +| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) classificará os resultados mostrando as consultorias mais novas primeiro. | +| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) classificará os resultados, mostrando os menos atualizados primeiro. | +| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) classificará os resultados, mostrando os mais atualizados primeiro. | +| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) mostrará apenas as consultorias que foram retiradas. | +| `created:YYYY-MM-DD` | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) mostrará apenas as consultorias criadas nessa data. | +| `updated:YYYY-MM-DD` | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) mostrará somente as consultorias atualizadas nesta data. | + +### Visualizar seus repositórios vulneráveis + +Para qualquer vulnerabilidade em {% data variables.product.prodname_advisory_database %}, você pode ver qual dos seus repositórios tem um alerta {% data variables.product.prodname_dependabot %} para essa vulnerabilidade. Para ver um repositório vulnerável, você deve ter acesso a {% data variables.product.prodname_dependabot_alerts %} para esse repositório. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)" + +1. Navegue até https://github.com/advisories. +2. Clique em uma consultoria. +3. Na parte superior da página da consultoria, clique em **Alertas do dependabot**. ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png) +4. Opcionalmente, para filtrar a lista, use a barra de pesquisa ou os menus suspensos. O menu suspenso "Organização" permite filtrar {% data variables.product.prodname_dependabot_alerts %} por proprietário (organização ou usuário). ![Barra de pesquisa e menus suspensos para filtrar alertas](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) +5. Para mais detalhes sobre a vulnerabilidade e para aconselhamento sobre como corrigir o repositório vulnerável clique no nome do repositório. ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index 2645d52350..879cb5bc55 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -12,6 +12,8 @@ versions: {% data reusables.github-actions.actions-spending-limit-brief %} Para obter mais informações, consulte "[Sobre limites de gastos](#about-spending-limits)". +Se você comprou {% data variables.product.prodname_enterprise %} por meio de um Contrato da Microsoft Enterprise, você pode conectar o ID da sua assinatura do Azure à sua conta corporativa para habilitar e pagar pelo uso de {% data variables.product.prodname_actions %} além dos valores incluindo na sua conta. 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)". + Os minutos são reiniciados todos os meses, mas o uso do armazenamento não. | Produto | Armazenamento | Minutos (por mês) | @@ -22,7 +24,7 @@ Os minutos são reiniciados todos os meses, mas o uso do armazenamento não. | {% data variables.product.prodname_team %} | 2 GB | 3.000 | | {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50.000 | -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. Usando 1.000 minutos macOS, consumiria 10.000 minutos incluídos em sua conta. +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. | Sistema operacional | Multiplicador de minutos | | ------------------- | ------------------------ | @@ -36,7 +38,7 @@ O armazenamento usado por um repositório é o armazenamento total usado por art {% note %} -**Nota:** Multiplicadores de minutos não se aplicam às taxas por minuto mostradas abaixo. +**Observação:** Os multiplicadores de minutos não se aplicam às taxas por minuto mostradas abaixo. {% endnote %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 57a18b62d8..df4e927a6c 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.package_registry.container-registry-beta-billing-note %} +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_registry %}, além dos valores incluindo na sua conta. 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)". + A transferência de dados é reiniciada todos os meses, mas o uso do armazenamento não. | Produto | Armazenamento | Transferência de dados (por mês) | diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 5ce1a7c6e5..0ad63cd0ce 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} Para obter mais informações sobre os preços para uso de {% data variables.product.prodname_actions %}, consulte "[Sobre cobrança para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". +Se você comprou {% data variables.product.prodname_enterprise %} por meio de um Contrato da Microsoft Enterprise, você pode conectar o ID da sua assinatura do Azure à sua conta corporativa para habilitar e pagar pelo uso de {% data variables.product.prodname_actions %} além dos valores incluindo na sua conta. 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)". + Assim que você definir um limite de gastos diferente de $ 0, você será responsável por todos os excedentes existentes no período de cobrança atual. Por exemplo, se a sua organização usa o {% data variables.product.prodname_team %}, não permite excessos, e cria artefatos de fluxo de trabalho que aumentam seu uso de armazenamento para o mês de 1.9GB para 2.1GB, você usará um pouco mais de armazenamento do que os 2GB que seu produto inclui. Como você não habilitou os excedentes, a sua próxima tentativa de criar um artefato de fluxo de trabalho falhará. Você não receberá uma fatura pelo excesso de 0.1GB naquele mês. No entanto, se você habilitar os excedentes, a sua primeira conta incluirá o 0,1 GB do excedente existente para o ciclo de cobrança atual, bem como qualquer superação adicional que você acumular. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index bbd37769ae..e1ba7be5c3 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} Para obter mais informações sobre os preços para uso de {% data variables.product.prodname_registry %}, consulte "[Sobre cobrança para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". +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_registry %}, além dos valores incluindo na sua conta. 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)". + Assim que você definir um limite de gastos diferente de $ 0, você será responsável por todos os excedentes existentes no período de cobrança atual. Por exemplo, se a sua organização usa o {% data variables.product.prodname_team %}, não permite excessos, e publica uma nova versão de um pacote privado que aumenta seu uso de armazenamento para o mês de 1.9GB para 2.1GB, a publicar a versão, você usará um pouco mais de armazenamento do que os 2GB que seu produto inclui. Como você não ativou os excessos, sua próxima tentativa de publicar uma versão do pacote irá falhar. Você não receberá uma fatura pelo excesso de 0.1GB naquele mês. No entanto, se você habilitar os excedentes, a sua primeira conta incluirá o 0,1 GB do excedente existente para o ciclo de cobrança atual, bem como qualquer superação adicional que você acumular. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 3e085cf03d..c481bd3cc3 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -23,8 +23,13 @@ O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os reposit {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -A página exibida permite que você habilite ou desabilite todas as funcionalidades de segurança e análise dos repositórios na sua organização. {% if currentVersion == "free-pro-team@latest" %}Se a sua organização ou a empresa à qual pertence tem uma licença para {% data variables.product.prodname_GH_advanced_security %}, a página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}. +A página exibida permite que você habilite ou desabilite todas as funcionalidades de segurança e análise dos repositórios na sua organização. +{% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@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.{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Funcionalidades de {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) {% endif %} @@ -42,24 +47,21 @@ Você pode habilitar ou desabilitar funcionalidades para todos os repositórios. 1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". 1. Em "Configurar recursos de segurança e análise" à direita do recurso, clique em **Desabilitar tudo** ou **Habilitar tudo**. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) {% endif %} 2. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) {% endif %} -1. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização. - {% if currentVersion == "free-pro-team@latest" %} +3. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) {% endif %} @@ -68,10 +70,9 @@ Você pode habilitar ou desabilitar funcionalidades para todos os repositórios. 1. Acesse as configurações de segurança e análise da sua organização. Para obter mais informações, consulte "[Exibir as configurações de segurança e análise](#displaying-the-security-and-analysis-settings)". 1. Em "Configurar funcionalidades de segurança e análise", à direita da funcionalidade, habilite ou desabilite a funcionalidade por padrão para novos repositórios {% if currentVersion == "free-pro-team@latest" %}, ou todos os novos repositórios privados,{% endif %} na sua organização. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) {% endif %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index f1116cda49..0d81855cd7 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -70,7 +70,7 @@ Além de gerenciar as configurações da organização, os proprietários da org {% 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** |{% if currentVersion == "free-pro-team@latest" %} +| Fechar, reabrir e atribuir todos os problemas e pull requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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** | @@ -150,8 +150,8 @@ Nesta seção, você pode encontrar os níveis de permissão de repositório nec | Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) em um repositório | | | | | **X** | | [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | | [Designar outras pessoas ou equipes para receber {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) para as dependências vulneráveis | | | | | **X** | -| Criar [consultorias de segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | -| Gerenciar acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %} (ver "[Gerenciar configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| Criar [consultorias de segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| Gerenciar acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %} (ver "[Gerenciar configurações de segurança e análise da sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | [Habilitar o gráfico de dependências](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) em um repositório privado | | | | | **X** | | [Visualizar as revisões de dependências](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md new file mode 100644 index 0000000000..0f1c18bea5 --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md @@ -0,0 +1,40 @@ +--- +title: Conectar uma assinatura do Azure à sua empresa +intro: 'Você pode usar o Contrato da Microsoft Enterprise para habilitar e pagar por {% data variables.product.prodname_actions %} e pelo uso de {% data variables.product.prodname_registry %}, além dos valores incluídos para a sua empresa.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise +versions: + free-pro-team: '*' +--- + +### Sobre as assinaturas do Azure e {% data variables.product.product_name %} + +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} Para obter mais informações, consulte "[Sobre a cobrança para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions) e "[Sobre cobrança para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." + +Após conectar a uma assinatura do Azure, você também poderá gerenciar seu limite de gastos. Para informações sobre como gerenciar e alterar o limite de gastos da sua conta, consulte "[Gerenciar o seu limite 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)" e "[Gerenciar o seu limite 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)". + +### Conectar a sua assinatura do Azure à sua conta corporativa + +Para conectar sua assinatura do Azure, você deve ter permissões de proprietário na assinatura. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Em "Informações de pagamento", clique em **Adicionar assinatura do Azure**. +1. Para entrar na sua conta da Microsoft, siga as instruções. +1. Revise a instrução de "Permissões solicitadas". Se você concordar com os termos, clique em **Aceitar**. +1. Em "Selecione uma assinatura", selecione o ID de Assinatura do Azure que você deseja conectar à sua empresa. +1. Clique em **Conectar**. + +### Desconectar a sua assinatura do Azure da sua conta corporativa + +Após desconectar a sua assinatura Azure da conta corporativa, seu uso não poderá mais exceder os valores incluídos no seu plano. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Em "Assinatura do Azure", à direita do ID de assinatura que você deseja desconectar, clique em **{% octicon "trashcan" aria-label="The trashcan icon" %}**. +1. Revise a instrução e clique em **Remover**. 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 2f7c5e8091..9775b94fc4 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 @@ -18,6 +18,7 @@ versions: {% link_in_list /about-enterprise-accounts %} {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %} {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %} + {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %} {% topic_link_in_list /managing-users-in-your-enterprise %} {% link_in_list /roles-in-an-enterprise %} {% link_in_list /inviting-people-to-manage-your-enterprise %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md index 8672d1d928..b944fa890c 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md @@ -31,7 +31,7 @@ Os proprietários corporativos têm controle total da empresa e podem executar t Os proprietários corporativos não podem acessar as configurações ou o conteúdo da organização, a menos que sejam incluídos como proprietário da organização ou recebam acesso direto a um repositório de propriedade da organização. Da mesma forma, os proprietários de organizações na sua empresa não têm acesso à empresa propriamente dita, a não ser que você os torne proprietários da empresa. -Você pode adicionar quantos proprietários corporativos desejar na sua empresa. {% if currentVersion == "free-pro-team@latest" %}Os proprietários de empresas devem ter uma conta pessoal em {% data variables.product.prodname_dotcom %}.{% endif %} Como prática recomendada, sugerimos que você converta apenas algumas pessoas da sua empresa em proprietários para reduzir o risco para a sua empresa. +Um proprietário da empresa só consumirá uma licença se for um proprietário ou integrante de pelo menos uma organização dentro da empresa. {% if currentVersion == "free-pro-team@latest" %}Os proprietários de empresas devem ter uma conta pessoal em {% data variables.product.prodname_dotcom %}.{% endif %} Como prática recomendada, sugerimos que você converta apenas algumas pessoas da sua empresa em proprietários para reduzir o risco para a sua empresa. ### Integrantes da empresa @@ -52,7 +52,7 @@ Os gerentes de cobrança só têm acesso às configurações de cobrança da sua - Exibir uma lista dos gerentes de cobrança - Adicionar ou remover outros gerentes de cobrança -Os gerentes de cobrança não têm acesso a organizações ou repositórios na sua empresa e não podem adicionar ou remover os proprietários da empresa. Os gerentes de cobrança devem ter uma conta pessoal no {% data variables.product.prodname_dotcom %}. +Os gerentes de cobrança só consumirão uma licença se forem um proprietário ou integrante de pelo menos uma organização dentro da empresa. Os gerentes de cobrança não têm acesso a organizações ou repositórios na sua empresa e não podem adicionar ou remover os proprietários da empresa. Os gerentes de cobrança devem ter uma conta pessoal no {% data variables.product.prodname_dotcom %}. ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 72515333ae..7e03a1e99d 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -15,6 +15,8 @@ versions: As contas corporativas atualmente estão disponíveis para clientes do {% data variables.product.prodname_enterprise %} que pagam com fatura. A cobrança de todas as organizações e instâncias {% data variables.product.prodname_ghe_server %} conectadas à sua conta corporativa é agregada em uma única fatura para todos os seus serviços pagos do {% data variables.product.prodname_dotcom_the_website %} (incluindo licenças pagas nas organizações, pacotes de dados do {% data variables.large_files.product_name_long %} e assinaturas de apps do {% data variables.product.prodname_marketplace %}). +{% if currentVersion == "free-pro-team@latest" %}{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 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){% endif %} + Para obter mais informações sobre como administrar gerentes de cobrança, consulte "[Convidar pessoas para gerenciar a sua empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". ### Exibir assinatura e uso da conta corporativa diff --git a/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md b/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md index d5a41ec910..037fe9b3ee 100644 --- a/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md +++ b/translations/pt-BR/content/github/site-policy/github-and-trade-controls.md @@ -63,15 +63,15 @@ O GitHub tem o compromisso de continuar oferecendo serviços públicos grátis d Para contas organizacionais pagas nessas regiões sancionadas, os usuários podem ter acesso limitado aos seus repositórios públicos, que foram rebaixados para repositórios arquivados somente leitura. Para contas organizacionais gratuitas nessas regiões sancionadas, no entanto, os usuários continuarão a ter acesso total a repositórios públicos gratuitos para projetos de código aberto (e Páginas públicas associadas), gists públicos e minutos de Ação alocados grátis. -O GitHub continuará defendendo junto com os EUA. regulators for the greatest possible access to code collaboration services to developers in Syria and Crimea, including private repositories. We believe that offering those services advances human progress, international communication, and the enduring U.S. de promoção da liberdade de expressão e da livre circulação da informação. +O GitHub continuará defendendo junto com os EUA. reguladores para o maior acesso possível aos serviços de colaboração de código para desenvolvedores da Síria e da Crimeia, incluindo repositórios privados. Acreditamos que oferecer a esses serviços é um avanço para o progresso humano, comunicação internacional, assim como para o fortalecimento para as restrições permanentes da política externa dos EUA. de promoção da liberdade de expressão e da livre circulação da informação. -Nacionais Designados Especialmente (SDNs) e outras partes negadas ou bloqueadas nos termos dos EUA and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Users may not use GitHub.com for or on behalf of such parties, generally including the Governments of sanctioned countries. +Nacionais Designados Especialmente (SDNs) e outras partes negadas ou bloqueadas nos termos dos EUA e outras leis aplicáveis, e certos funcionários do governo podem receber restrições para acessar ou usar o GitHub, onde quer que se encontrem. Os usuários não podem usar o GitHub.com para ou em nome de tais entidades, incluindo, de modo geral, os governos de países sancionados. -GitHub services are not available to developers located or otherwise resident in North Korea. +Os serviços do GitHub não estão disponíveis para desenvolvedores localizados ou residentes na Coreia do Norte. #### Como você define esses usuários específicos? -Se o GitHub determinar que um usuário ou cliente está localizado em uma região sujeita às restrições de controle de negociação dos EUA, ou que um usuário está restrito pelas sanções econômicas dos EUA, então a conta afiliada será limitada para cumprir esses requisitos legais. trade control restrictions for which GitHub does not yet have a license from the U.S. government, or a user is otherwise restricted under U.S. economic sanctions, then the affiliated account will be restricted to comply with those legal requirements. A determinação da localização do usuário e cliente para implementar essas restrições legais deriva de várias fontes, incluindo endereços IP e histórico de pagamentos. A nacionalidade e a etnia não são utilizadas para sinalizar usuários para restrições de sanções. +Se o GitHub determinar que um usuário ou cliente está localizado em uma região sujeita às restrições de controle de negociação dos EUA, ou que um usuário está restrito pelas sanções econômicas dos EUA, então a conta afiliada será limitada para cumprir esses requisitos legais. restrições de controle de comércio para as quais o GitHub ainda não possui uma licença dos EUA. governo, ou um usuário está restrito de outra forma nos EUA. economic sanctions, then the affiliated account will be restricted to comply with those legal requirements. A determinação da localização do usuário e cliente para implementar essas restrições legais deriva de várias fontes, incluindo endereços IP e histórico de pagamentos. A nacionalidade e a etnia não são utilizadas para sinalizar usuários para restrições de sanções. #### Como as contas da organização são impactadas? @@ -104,4 +104,4 @@ Pursuant to the license we have received from OFAC, we are restoring all cloud s #### Can you clarify availability of GitHub to Cuban developers? GitHub cloud services, both free and paid, are generally available to developers located in Cuba. -Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. and other applicable law, and certain government officials may be restricted from accessing or using GitHub, wherever located. Além disso, os usuários não podem usar o GitHub.com para ou em nome de tais entidades, incluindo, de modo geral, os governos de países sancionados. +Specially Designated Nationals (SDNs), other denied or blocked parties under U.S. e outras leis aplicáveis, e certos funcionários do governo podem receber restrições para acessar ou usar o GitHub, onde quer que se encontrem. Além disso, os usuários não podem usar o GitHub.com para ou em nome de tais entidades, incluindo, de modo geral, os governos de países sancionados. diff --git a/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md index 62cc0585b7..3ca24a2a48 100644 --- a/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md +++ b/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md @@ -10,68 +10,68 @@ versions: free-pro-team: '*' --- -Effective date: **January 29, 2021** +Entrada em vigor: **29 de janeiro de 2021** -O GitHub fornece um grande acordo de transparência em relação à forma como usamos seus dados, como os coletamos e com quem compartilhamos. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github). +O GitHub fornece um grande acordo de transparência em relação à forma como usamos seus dados, como os coletamos e com quem compartilhamos. Para essa finalidade, disponibilizamos esta página, que detalha os [nossos subprocessadores](#github-subprocessors) e como usamos [cookies](#cookies-on-github). ### Subprocessadores GitHub Quando compartilhamos suas informações com terceiros subprocessadores, tais como nossos fornecedores e provedores de serviços, permanecemos responsáveis por elas. Trabalhamos muito duro para manter sua confiança quando trazemos novos fornecedores, e exigimos que todos os fornecedores se submetam a contratos de proteção de dados conosco que restringem seu processamento de Informações Pessoais dos Usuários (conforme definido na [Declaração de Privacidade](/articles/github-privacy-statement/)). -| Nome do subprocessador | Descrição do processamento | Local do Processamento | Localização corporativa | -|:------------------------ |:--------------------------------------------------------------------- |:---------------------- |:----------------------- | -| Automattic | Serviço de blogs | Estados Unidos | Estados Unidos | -| AWS Amazon | Hospedagem de dados | Estados Unidos | Estados Unidos | -| Braintree (PayPal) | Processador de pagamento de assinatura com cartão de crédito | Estados Unidos | Estados Unidos | -| Clearbit | Serviço de enriquecimento de dados de marketing | Estados Unidos | Estados Unidos | -| Discourse | Provedor de software do fórum comunitário | Estados Unidos | Estados Unidos | -| Eloqua | Automatização da campanha marketing | Estados Unidos | Estados Unidos | -| Google Apps | Infraestrutura interna da empresa | Estados Unidos | Estados Unidos | -| MailChimp | Fornecedor de serviços de correio para emissão de bilhetes a clientes | Estados Unidos | Estados Unidos | -| Mailgun | Provedor de serviços de correio transacional | Estados Unidos | Estados Unidos | -| Microsoft | Microsoft Services | Estados Unidos | Estados Unidos | -| Monday.com | Colaboração da equipe e plataforma de gerenciamento de projetos | Estados Unidos | Israel | -| Nexmo | Provedor de notificação de SMS | Estados Unidos | Estados Unidos | -| Salesforce.com | Gerenciamento de relacionamento com clientes | Estados Unidos | Estados Unidos | -| Sentry.io | Provedor de monitoramento de aplicativo | Estados Unidos | Estados Unidos | -| Stripe | Provedor de pagamentos | Estados Unidos | Estados Unidos | -| Twilio & Twilio Sendgrid | SMS notification provider & transactional mail service provider | Estados Unidos | Estados Unidos | -| Zendesk | Sistema de bilhetagem de suporte ao cliente | Estados Unidos | Estados Unidos | -| Zuora | Sistema de faturamento corporativo | Estados Unidos | Estados Unidos | +| Nome do subprocessador | Descrição do processamento | Local do Processamento | Localização corporativa | +|:------------------------ |:--------------------------------------------------------------------------- |:---------------------- |:----------------------- | +| Automattic | Serviço de blogs | Estados Unidos | Estados Unidos | +| AWS Amazon | Hospedagem de dados | Estados Unidos | Estados Unidos | +| Braintree (PayPal) | Processador de pagamento de assinatura com cartão de crédito | Estados Unidos | Estados Unidos | +| Clearbit | Serviço de enriquecimento de dados de marketing | Estados Unidos | Estados Unidos | +| Discourse | Provedor de software do fórum comunitário | Estados Unidos | Estados Unidos | +| Eloqua | Automatização da campanha marketing | Estados Unidos | Estados Unidos | +| Google Apps | Infraestrutura interna da empresa | Estados Unidos | Estados Unidos | +| MailChimp | Fornecedor de serviços de correio para emissão de bilhetes a clientes | Estados Unidos | Estados Unidos | +| Mailgun | Provedor de serviços de correio transacional | Estados Unidos | Estados Unidos | +| Microsoft | Microsoft Services | Estados Unidos | Estados Unidos | +| Monday.com | Colaboração da equipe e plataforma de gerenciamento de projetos | Estados Unidos | Israel | +| Nexmo | Provedor de notificação de SMS | Estados Unidos | Estados Unidos | +| Salesforce.com | Gerenciamento de relacionamento com clientes | Estados Unidos | Estados Unidos | +| Sentry.io | Provedor de monitoramento de aplicativo | Estados Unidos | Estados Unidos | +| Stripe | Provedor de pagamentos | Estados Unidos | Estados Unidos | +| Twilio & Twilio Sendgrid | Provedor de notificação de SMS & Provedor de serviço de e-mail transacional | Estados Unidos | Estados Unidos | +| Zendesk | Sistema de bilhetagem de suporte ao cliente | Estados Unidos | Estados Unidos | +| Zuora | Sistema de faturamento corporativo | Estados Unidos | Estados Unidos | Quando trouxermos um novo subprocessador que lida com as Informações Pessoais de nossos Usuários, ou removermos um subprocessador, ou mudarmos a forma como usamos um subprocessador, atualizaremos esta página. Se você tiver dúvidas ou preocupações sobre um novo subprocessador, ficaremos felizes em ajudar. Entre em contato conosco via {% data variables.contact.contact_privacy %}. ### Cookies no GitHub -GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Consulte nossa [Declaração de privacidade](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) se você quiser saber mais informações sobre cookies e sobre como e por que os usamos. +O GitHub usa cookies para fornecer e proteger nossos sites, bem como analisar o uso dos nossos sites, para oferecer a você uma ótima experiência de usuário. Consulte nossa [Declaração de privacidade](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) se você quiser saber mais informações sobre cookies e sobre como e por que os usamos. -Since the number and names of cookies may change, the table below may be updated from time to time. +Como o número e os nomes dos cookies podem mudar, a tabela abaixo pode ser atualizada de vez em quando. -| Provedor de serviço | Nome do cookie | Descrição | Vencimento* | -|:------------------- |:------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- | -| GitHub | `app_manifest_token` | Este cookie é usado durante o fluxo do manifesto do aplicativo para manter o estado do fluxo durante o redirecionamento para buscar uma sessão do usuário. | cinco minutos | -| GitHub | `_device_id` | This cookie is used to track recognized devices for security purposes. | um ano | -| GitHub | `dotcom_user` | Este cookie é usado para sinalizar que o usuário já está logado. | um ano | -| GitHub | `_gh_ent` | Este cookie é usado para aplicação temporária e para o estado da estrutura entre páginas, como em que etapa o cliente se encontra em um processo de várias etapas. | duas semanas | -| GitHub | `_gh_sess` | Este cookie é usado para aplicação temporária e para o estado do framework entre páginas, como por exemplo, em qual etapa o usuário está em um formulário de várias etapas. | sessão | -| GitHub | `gist_oauth_csrf` | Este cookie é definido pelo Gist para garantir que o usuário que iniciou o fluxo de autenticação seja o mesmo usuário que o completa. | excluído quando o estado do oauth é validado | -| GitHub | `gist_user_session` | Este cookie é usado pelo Gist ao ser executado em um host separado. | duas semanas | -| GitHub | `has_recent_activity` | Este cookie é usado para impedir a exibição de intersticial de segurança para usuários que visitaram o aplicativo recentemente. | uma hora | -| GitHub | `__Host-gist_user_session_same_site` | Este cookie foi definido para garantir que os navegadores que suportam cookies do SameSite possam verificar se uma solicitação é originária do GitHub. | duas semanas | -| GitHub | `__Host-user_session_same_site` | Este cookie foi definido para garantir que os navegadores que suportam cookies do SameSite possam verificar se uma solicitação é originária do GitHub. | duas semanas | -| GitHub | `logged_in` | Este cookie é usado para sinalizar que o usuário já está logado. | um ano | -| GitHub | `marketplace_repository_ids` | Este cookie é usado para o fluxo de instalação do marketplace. | uma hora | -| GitHub | `marketplace_suggested_target_id` | Este cookie é usado para o fluxo de instalação do marketplace. | uma hora | -| GitHub | `_octo` | This cookie is used for session management including caching of dynamic content, conditional feature access, support request metadata, and first party analytics. | um ano | -| GitHub | `org_transform_notice` | Este cookie é usado para fornecer aviso durante a transformação da organização. | uma hora | -| GitHub | `private_mode_user_session` | Este cookie é usado para solicitações de autenticação da empresa. | duas semanas | -| GitHub | `saml_csrf_token` | Este cookie é definido pelo método de caminho de autenticação SAML para associar um token ao cliente. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | -| GitHub | `saml_csrf_token_legacy` | Este cookie é definido pelo método de caminho de autenticação SAML para associar um token ao cliente. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | -| GitHub | `saml_return_to` | Este cookie é definido pelo método de caminho de autenticação SAML para manter o estado durante o loop de autenticação SAML. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | -| GitHub | `saml_return_to_legacy` | Este cookie é definido pelo método de caminho de autenticação SAML para manter o estado durante o loop de autenticação SAML. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | -| GitHub | `tz` | This cookie allows us to customize timestamps to your time zone. | sessão | -| GitHub | `user_session` | Este cookie é usado para fazer seu login. | duas semanas | +| Provedor de serviço | Nome do cookie | Descrição | Vencimento* | +|:------------------- |:------------------------------------ |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- | +| GitHub | `app_manifest_token` | Este cookie é usado durante o fluxo do manifesto do aplicativo para manter o estado do fluxo durante o redirecionamento para buscar uma sessão do usuário. | cinco minutos | +| GitHub | `_device_id` | Este cookie é usado para rastrear dispositivos reconhecidos para fins de segurança. | um ano | +| GitHub | `dotcom_user` | Este cookie é usado para sinalizar que o usuário já está logado. | um ano | +| GitHub | `_gh_ent` | Este cookie é usado para aplicação temporária e para o estado da estrutura entre páginas, como em que etapa o cliente se encontra em um processo de várias etapas. | duas semanas | +| GitHub | `_gh_sess` | Este cookie é usado para aplicação temporária e para o estado do framework entre páginas, como por exemplo, em qual etapa o usuário está em um formulário de várias etapas. | sessão | +| GitHub | `gist_oauth_csrf` | Este cookie é definido pelo Gist para garantir que o usuário que iniciou o fluxo de autenticação seja o mesmo usuário que o completa. | excluído quando o estado do oauth é validado | +| GitHub | `gist_user_session` | Este cookie é usado pelo Gist ao ser executado em um host separado. | duas semanas | +| GitHub | `has_recent_activity` | Este cookie é usado para impedir a exibição de intersticial de segurança para usuários que visitaram o aplicativo recentemente. | uma hora | +| GitHub | `__Host-gist_user_session_same_site` | Este cookie foi definido para garantir que os navegadores que suportam cookies do SameSite possam verificar se uma solicitação é originária do GitHub. | duas semanas | +| GitHub | `__Host-user_session_same_site` | Este cookie foi definido para garantir que os navegadores que suportam cookies do SameSite possam verificar se uma solicitação é originária do GitHub. | duas semanas | +| GitHub | `logged_in` | Este cookie é usado para sinalizar que o usuário já está logado. | um ano | +| GitHub | `marketplace_repository_ids` | Este cookie é usado para o fluxo de instalação do marketplace. | uma hora | +| GitHub | `marketplace_suggested_target_id` | Este cookie é usado para o fluxo de instalação do marketplace. | uma hora | +| GitHub | `_octo` | Este cookie é usado para o gerenciamento de sessões, incluindo o cache de conteúdo dinâmico, acesso condicional a recursos, suporte a metadados solicitados e análise da primeira parte. | um ano | +| GitHub | `org_transform_notice` | Este cookie é usado para fornecer aviso durante a transformação da organização. | uma hora | +| GitHub | `private_mode_user_session` | Este cookie é usado para solicitações de autenticação da empresa. | duas semanas | +| GitHub | `saml_csrf_token` | Este cookie é definido pelo método de caminho de autenticação SAML para associar um token ao cliente. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | +| GitHub | `saml_csrf_token_legacy` | Este cookie é definido pelo método de caminho de autenticação SAML para associar um token ao cliente. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | +| GitHub | `saml_return_to` | Este cookie é definido pelo método de caminho de autenticação SAML para manter o estado durante o loop de autenticação SAML. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | +| GitHub | `saml_return_to_legacy` | Este cookie é definido pelo método de caminho de autenticação SAML para manter o estado durante o loop de autenticação SAML. | até que o usuário feche o navegador ou conclua a solicitação de autenticação | +| GitHub | `tz` | Este cookie nos permite personalizar os horários para seu fuso horário. | sessão | +| GitHub | `user_session` | Este cookie é usado para fazer seu login. | duas semanas | _*_ A data de **expiração** para os cookies listados abaixo geralmente se aplicam em uma base contínua. -(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. Por exemplo, podemos incorporar conteúdo, como vídeos, de outro site que define um cookie. Embora tentemos minimizar esses cookies de terceiros, nem sempre podemos controlar quais cookies esse conteúdo de terceiros define. +(!) Observe que, embora limitemos o uso de cookies de terceiros aos que forem necessários para fornecer funcionalidade externa ao processar conteúdo externo, certas páginas no nosso site podem definir outros cookies de terceiros. Por exemplo, podemos incorporar conteúdo, como vídeos, de outro site que define um cookie. Embora tentemos minimizar esses cookies de terceiros, nem sempre podemos controlar quais cookies esse conteúdo de terceiros define. diff --git a/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site.md b/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site.md index 3e61174bdd..a82c7e1632 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site.md +++ b/translations/pt-BR/content/github/working-with-github-pages/creating-a-github-pages-site.md @@ -20,8 +20,6 @@ versions: {% 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 %} @@ -33,6 +31,8 @@ versions: {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% data reusables.pages.navigate-site-repo %} {% data reusables.pages.decide-publishing-source %} 3. Se a fonte de publicação que você escolheu já existe, navegue até ela. Caso contrário, crie a fonte de publicação. diff --git a/translations/pt-BR/content/rest/overview/libraries.md b/translations/pt-BR/content/rest/overview/libraries.md index f69fb0c166..1086cfdcd5 100644 --- a/translations/pt-BR/content/rest/overview/libraries.md +++ b/translations/pt-BR/content/rest/overview/libraries.md @@ -25,7 +25,7 @@ versions: ### Clojure -Nome da biblioteca | Repositório |---|---| **Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles) +Library name | Repository |---|---| **Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles) ### Dart @@ -57,7 +57,7 @@ Nome da biblioteca | Repositório | |---|---| **NodeJS GitHub library**| [pksunk ### Julia -Nome da biblioteca | Repositório | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl) +Library name | Repository | |---|---| **GitHub.jl**|[WestleyArgentum/GitHub.jl](https://github.com/WestleyArgentum/GitHub.jl) ### OCaml @@ -65,11 +65,11 @@ Nome da biblioteca | Repositório | |---|---| **ocaml-github**|[mirage/ocaml-git ### Perl -Nome da biblioteca | Repositório | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub) +Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub) ### PHP -Nome da biblioteca | Repositório |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI) +Nome da biblioteca | Repositório |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GitHubAPI](https://github.com/FlexyProject/GitHubAPI) ### Python diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md index 7adcd7c201..e9c784ea5b 100644 --- a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md @@ -129,7 +129,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar > { > "message": "Bad credentials", -> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -141,7 +141,7 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f > 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" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -364,7 +364,7 @@ Se você exceder o limite de taxa, uma resposta do erro retorna: > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#rate-limiting" > } ``` @@ -409,7 +409,7 @@ Se seu aplicativo acionar este limite de taxa, você receberá uma resposta info > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#abuse-rate-limits" > } ``` diff --git a/translations/pt-BR/data/release-notes/2-20/0.yml b/translations/pt-BR/data/release-notes/2-20/0.yml index 840753ba44..c7d94eed08 100644 --- a/translations/pt-BR/data/release-notes/2-20/0.yml +++ b/translations/pt-BR/data/release-notes/2-20/0.yml @@ -30,9 +30,9 @@ sections: - 'Em uma revisão de pull request, um aviso é exibido se um comentário linha múltipla for truncado. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' - 'Os usuários podem ver seus logs de auditoria na aba "Log de segurança" nas suas configurações pessoais. {% comment %} https://github.com/github/github/pull/123041{% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - Entradas duplicadas de webhook no banco de dados podem gerar falha de atualizações de versões anteriores. (atualizada 2020-02-26) diff --git a/translations/pt-BR/data/release-notes/2-20/1.yml b/translations/pt-BR/data/release-notes/2-20/1.yml index 863011a60f..57f15491b1 100644 --- a/translations/pt-BR/data/release-notes/2-20/1.yml +++ b/translations/pt-BR/data/release-notes/2-20/1.yml @@ -8,9 +8,9 @@ sections: - 'Os comentários de revisão de PR com valores inesperados para "position" ou "original_position" geraram falha nas importações. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' - 'As entradas duplicadas de webhook no banco de dados podem gerar falha de atualizações de versões anteriores. {% 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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - 'As atualizações e as definições de atualização irão falhar se as configurações em segundo plano do trabalhador forem personalizadas. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/10.yml b/translations/pt-BR/data/release-notes/2-20/10.yml index 518926744f..32f502bf50 100644 --- a/translations/pt-BR/data/release-notes/2-20/10.yml +++ b/translations/pt-BR/data/release-notes/2-20/10.yml @@ -11,9 +11,9 @@ sections: - 'Tentar atribuir a revisão de código a um integrante de uma equipe vazia geraria "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}' - 'A atribuição da revisão do código que usa o algoritmo de balanceamento de carga pode ser atribuída repetidamente ao mesmo integrante da equipe. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/11.yml b/translations/pt-BR/data/release-notes/2-20/11.yml index 5456f56910..df5d0cc5c6 100644 --- a/translations/pt-BR/data/release-notes/2-20/11.yml +++ b/translations/pt-BR/data/release-notes/2-20/11.yml @@ -10,9 +10,9 @@ sections: - 'Trabalhos em segundo plano incorretos podem tentar ser executados em instâncias configuradas como réplicas passivas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - 'Os repositórios internos não foram incluídos corretamente nos resultados de pesquisa para as orgs habilitadas com SAML. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/12.yml b/translations/pt-BR/data/release-notes/2-20/12.yml index a0af2cb8cf..5d6a8d8270 100644 --- a/translations/pt-BR/data/release-notes/2-20/12.yml +++ b/translations/pt-BR/data/release-notes/2-20/12.yml @@ -8,9 +8,9 @@ sections: changes: - 'Melhorias no dimensionamento do HAProxy {% comment %} https://github.com/github/enterprise2/pull/21383 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/13.yml b/translations/pt-BR/data/release-notes/2-20/13.yml index 76399853c2..1c384fd554 100644 --- a/translations/pt-BR/data/release-notes/2-20/13.yml +++ b/translations/pt-BR/data/release-notes/2-20/13.yml @@ -13,9 +13,9 @@ sections: - 'Os problemas não puderam ser classificados por *Atualizações recentes* nos repositórios migrados para uma nova instância. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/github/pull/149330 {% endcomment %}' - 'A página 404 continha links de contato e links status do GitHub.com na nota de rodapé. {% comment %} https://github.com/github/github/pull/151316 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/14.yml b/translations/pt-BR/data/release-notes/2-20/14.yml index 976753b25d..2e3e9d011a 100644 --- a/translations/pt-BR/data/release-notes/2-20/14.yml +++ b/translations/pt-BR/data/release-notes/2-20/14.yml @@ -4,9 +4,9 @@ sections: - 'Resolveu um problema que poderia gerar alto uso da CPU ao gerar modelos de configuração do sistema. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - 'Alterações recentes nas alocações de memória podem gerar uma degradação no desempenho do sistema {% comment %} https://github.com/github/enterprise2/pull/22067 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/16.yml b/translations/pt-BR/data/release-notes/2-20/16.yml index deee6c4ab3..0d3b497e48 100644 --- a/translations/pt-BR/data/release-notes/2-20/16.yml +++ b/translations/pt-BR/data/release-notes/2-20/16.yml @@ -4,9 +4,9 @@ sections: - 'Uma verificação de saúde do serviço causou o crescimento da sessão, o que gerou um esgotamento do sistema de arquivos. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - 'A atualização que usa um hotpatch pode falhar com um erro: `''libdbi1'' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/17.yml b/translations/pt-BR/data/release-notes/2-20/17.yml index a2ef290194..b6c66a9dc2 100644 --- a/translations/pt-BR/data/release-notes/2-20/17.yml +++ b/translations/pt-BR/data/release-notes/2-20/17.yml @@ -4,9 +4,9 @@ sections: - '**MÉDIO**: ImageMagick foi atualizado para o endereço [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 %}' - 'Os pacotes foram atualizados para as últimas versões de segurança. {% 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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/18.yml b/translations/pt-BR/data/release-notes/2-20/18.yml index 374207ae75..eabe2c16e2 100644 --- a/translations/pt-BR/data/release-notes/2-20/18.yml +++ b/translations/pt-BR/data/release-notes/2-20/18.yml @@ -17,9 +17,9 @@ sections: - 'Remova o requisito de impressões digitais SSH nos arquivos "ghe-migrator", pois ele sempre pode ser computado. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' - 'Os manifestos do aplicativo GitHub agora incluem o 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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/19.yml b/translations/pt-BR/data/release-notes/2-20/19.yml index 401e533cae..a84929c005 100644 --- a/translations/pt-BR/data/release-notes/2-20/19.yml +++ b/translations/pt-BR/data/release-notes/2-20/19.yml @@ -5,9 +5,9 @@ sections: bugs: - 'A mensagem da conta corporativa "Confirmar requisito de dois fatores" estava incorreta. {% comment %} https://github.com/github/github/pull/158737 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/2.yml b/translations/pt-BR/data/release-notes/2-20/2.yml index b41cb1a5ae..17e5bd727b 100644 --- a/translations/pt-BR/data/release-notes/2-20/2.yml +++ b/translations/pt-BR/data/release-notes/2-20/2.yml @@ -15,9 +15,9 @@ sections: changes: - 'O utilitário da linha de comando `ghe-license-usage ` incliu uma opção `--unencrypted` nova para proporcionar visibilidade no arquivo de uso da licença exportado. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - 'As atualizações e as definições de atualização irão falhar se as configurações em segundo plano do trabalhador forem personalizadas. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/20.yml b/translations/pt-BR/data/release-notes/2-20/20.yml index 01122c4f75..0d04588902 100644 --- a/translations/pt-BR/data/release-notes/2-20/20.yml +++ b/translations/pt-BR/data/release-notes/2-20/20.yml @@ -7,9 +7,9 @@ sections: bugs: - 'Os usuários suspensos foram incluídos na lista de usuários sugeridos, ocultando potencialmente usuários não suspensos. {% 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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/21.yml b/translations/pt-BR/data/release-notes/2-20/21.yml index 7fdd9bf91c..b73520361e 100644 --- a/translations/pt-BR/data/release-notes/2-20/21.yml +++ b/translations/pt-BR/data/release-notes/2-20/21.yml @@ -6,9 +6,9 @@ sections: - 'Os logs de babeld não tinham um separador entre segundos e microssegundos. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' - 'Quando a política de "alteração de visibilidade do repositório" na conta corporativa foi definida como "Habilitada", os proprietários da organização não conseguiram alterar a visibilidade dos repositórios na organização. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/22.yml b/translations/pt-BR/data/release-notes/2-20/22.yml index e11a740e44..ba494ad034 100644 --- a/translations/pt-BR/data/release-notes/2-20/22.yml +++ b/translations/pt-BR/data/release-notes/2-20/22.yml @@ -10,9 +10,9 @@ sections: - 'A sincronização de pull request em repositórios com muitas referências pode fazer com que as filas de trabalhador sejam atrasadas. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' - 'Ao efetuar o login após tentar visitar uma página específica, as pessoas eram enviadas para a página inicial em vez de serem enviadas para o seu destino pretendido. {% comment %} https://github. O/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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/23.yml b/translations/pt-BR/data/release-notes/2-20/23.yml index 102d790d96..efd84f457e 100644 --- a/translations/pt-BR/data/release-notes/2-20/23.yml +++ b/translations/pt-BR/data/release-notes/2-20/23.yml @@ -4,9 +4,9 @@ sections: - '**BAIXO:** Alto uso da CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN, o que resulta em em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/3.yml b/translations/pt-BR/data/release-notes/2-20/3.yml index ac451b6545..c777efa565 100644 --- a/translations/pt-BR/data/release-notes/2-20/3.yml +++ b/translations/pt-BR/data/release-notes/2-20/3.yml @@ -3,9 +3,9 @@ sections: bugs: - 'As atualizações e as atualizações de configurações poderiam falhar se as configurações em segundo plano do trabalhador tivessem sido personalizadas. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/4.yml b/translations/pt-BR/data/release-notes/2-20/4.yml index 571f3d8b57..4722d8ab26 100644 --- a/translations/pt-BR/data/release-notes/2-20/4.yml +++ b/translations/pt-BR/data/release-notes/2-20/4.yml @@ -6,9 +6,9 @@ sections: - 'Ao fazer push em um Gist, uma exceção pode ser acionada durante o hook de post-receive. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' - '`ghe-repl-status` pode falhar ao tentar exibir repositórios que não foram totalmente replicados. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/5.yml b/translations/pt-BR/data/release-notes/2-20/5.yml index 577dea2f15..ee855bc2c7 100644 --- a/translations/pt-BR/data/release-notes/2-20/5.yml +++ b/translations/pt-BR/data/release-notes/2-20/5.yml @@ -8,9 +8,9 @@ sections: - 'O campo `package` das vulnerabilidades de segurança não pôde ser consultado por meio da API do GraphQL. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' - 'A alteração um repositório de *público* para *interno* exibiu uma mensagem de cobrança irrelevante. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/6.yml b/translations/pt-BR/data/release-notes/2-20/6.yml index c0350f9aab..46d74deacc 100644 --- a/translations/pt-BR/data/release-notes/2-20/6.yml +++ b/translations/pt-BR/data/release-notes/2-20/6.yml @@ -16,9 +16,9 @@ sections: - 'Quando o trabalho do cron do orchestrator-cliente falhou, vários e-mails foram enviados para a conta raiz. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' - 'Quando um provedor de identidade externo controlou o status de administrador do site do usuário, os usuários não puderem ser rebaixados por meio do utilitário da linha de comando. {% 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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/7.yml b/translations/pt-BR/data/release-notes/2-20/7.yml index 730ffbdac2..6623676cc2 100644 --- a/translations/pt-BR/data/release-notes/2-20/7.yml +++ b/translations/pt-BR/data/release-notes/2-20/7.yml @@ -10,9 +10,9 @@ sections: - 'A coleção de lixo de arquivos temporários pode gerar um erro de validação de licença. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' - 'Em algumas situações, inclusive quando um repositório é criado pela primeira vez, o hook de pre-receive seria executado sem um valor preenchido para a variável 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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/8.yml b/translations/pt-BR/data/release-notes/2-20/8.yml index db80bec829..3788df27e8 100644 --- a/translations/pt-BR/data/release-notes/2-20/8.yml +++ b/translations/pt-BR/data/release-notes/2-20/8.yml @@ -9,9 +9,9 @@ sections: - 'A suspensão automática de um usuário através do SSO não foi concluída, caso o atributo de e-mail do SAML tenha um revestimento diferente do do e-mail do usuário do GitHub. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' - 'Restaurar a associação de um usuário a uma organização não instrumentou o ator em cargas de webhook e log de auditoria. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-20/9.yml b/translations/pt-BR/data/release-notes/2-20/9.yml index e1f7da7cbf..e96c186e4d 100644 --- a/translations/pt-BR/data/release-notes/2-20/9.yml +++ b/translations/pt-BR/data/release-notes/2-20/9.yml @@ -6,9 +6,9 @@ sections: bugs: - 'As instâncias do GitHub Enterprise Server voltadas para a Internet podem ser indexadas pelos mecanismos de busca. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/0.yml b/translations/pt-BR/data/release-notes/2-21/0.yml index 42f8fd9df2..3d94e72104 100644 --- a/translations/pt-BR/data/release-notes/2-21/0.yml +++ b/translations/pt-BR/data/release-notes/2-21/0.yml @@ -9,63 +9,63 @@ sections: - '[Os cartões de projeto incluem uma seção de pull requests vinculados](https://github. log/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) para que um usuário possa ver qual trabalho de desenvolvimento está relacionado ao problema diretamente no quadro de projeto. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' - 'Há um novo conjunto de [pontos extremidade para "Excluir reações"](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) na API de Reações. Os pontos de extremidade "Excluir reações" existentes serão suspensos no início de 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - 'Há um novo conjunto de [pontos de extremidade da API de equipes](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) que permitirá que o GitHub dimensione e apoie a API de equipes no longo prazo. Os pontos de extremidade da API serão suspensos no início de 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' - - 'Users can [create links between issues and pull requests](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) without needing to use closing keywords in the pull request description. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - 'Os usuários podem [criar links entre problemas e pull requests](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) sem a necessidade de fechar palavras-chave na descrição do pull request. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' security_fixes: - - 'An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - 'Uma vulnerabilidade de controle de acesso imprópria foi identificada na API do GitHub Enterprise Server que permitiu que um integrante da organização aumentasse as permissões e recebesse acesso a repositórios não autorizados dentro de uma organização. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server anteriores à versão 2.21. Emitimos [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) em resposta a este problema. A vulnerabilidade foi relatada por meio do [programa Bug Bounty do GitHub](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' bugs: - - 'If a user with push access minimized another user''s comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}' - - 'Users could accidentally merge to master from the issue template editor and blob editor. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' - - 'When a user deleted an account from GitHub, the audit log records did not correctly show organization removal records. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' - - 'The gist avatar for the current user would link to a non-existent URL. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' - - 'The organization repositories tab count did not include internal repositories. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' - - 'Clicking the "Show All Teams" button when transferring a repository caused a 500 error. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' - - 'Long filenames could cause overflow issues when showing the ''Changed since last view'' label or the ''Show rich'' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}' - - 'Hovercards for organization teams misreported their member size. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' - - 'The pull request review comment popup window had a scrolling issue. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' - - 'Haproxy could become saturated causing a slowdown in git operations. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' - - 'The Dependency Graph feature was not automatically enabled after HA replica promotion. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' - - 'A timeout could be triggered on the releases index page for repositories with thousands of draft pull requests. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' - - 'It was not possible to filter pull requests by both state and draft at the same time. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' - - 'If a pull request changed a submodule pointer, then clicking "Edit file" on that submodule file from the "Files changed" tab of the pull request page caused a 404 error. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' - - 'It was not possible to add users to an organization, or delete the organization, following the bulk removal of all users and admins from that organization. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' - - 'Review comments against files containing diacritics and non-Latin characters in the filename on the "Files changed" page would disappear when the page is reloaded. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - 'The state of the "Viewed" checkbox was not retained for files containing diacritics and non-Latin characters in the filename on the "Files changed" page. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - 'Pull requests showed the "Approved" badge when not all required reviews were in place. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' - - 'The tag dropdown was empty when searching for a tag in repositories with more than 100 tags. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' - - 'Pull request pages showing annotations with non UTF-8 titles could encounter encoding errors in view rendering. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' - - 'A race condition for refresh on the OAuth page could cause a redirect to be executed twice. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' - - 'The "Personal Access Tokens" page would timeout if there are more than 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' - - 'Scheduled LDAP User and Team Sync jobs could be started while previously scheduled Sync jobs were still in process. A locking mechanism has been implemented to prevent new Sync jobs from starting if one is still running. {% 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 %}' + - 'Se um usuário com acesso push minimizou o comentário de outro usuário, o autor do comentário poderia minimizá-lo mesmo se não tivesse privilégios suficientes. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}' + - 'Os usuários podem acidentalmente fazer merge para mestre a partir do editor de modelos de problemas e blob. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' + - 'Quando um usuário exclui uma conta do GitHub, os registros do log de auditoria não mostraram corretamente os registros de remoção da organização. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' + - 'O avatar do gist para o usuário atual faria um link para uma URL inexistente. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' + - 'A aba de contagem de repositórios da organização não incluiu repositórios internos. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' + - 'Ao transferir um repositório, clicar no botão "Mostrar Todas as Equipes" gerou um erro 500. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' + - 'Os nomes de arquivos longos podem gerar um excesso de fluxo de problemas ao mostrar a etiqueta "Alterado desde a última vista" ou a alternância de diff de "Mostrar enriquecido" na vista dos arquivos diff. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}' + - 'Os cartões de vista virtual para equipes da organização relataram mal o tamanho do integrante. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' + - 'A janela pop-up de comentário do pull request teve um problema de deslocamento. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' + - 'Haproxy pode saturar-se, gerando lentidão nas operações do git. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' + - 'O recurso Gráfico de Dependência não foi automaticamente habilitado após a promoção da réplica de HA. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' + - 'É possível que um tempo limite seja acionado na página de índice de lançamentos para repositórios com milhares de rascunhos de pull requests. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' + - 'Não foi possível filtrar os pull requests por estado e rascunho ao mesmo tempo. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' + - 'Se um pull request mudou um ponteiro do submódulo, clicar em "Editar arquivo" nesse arquivo do submódulo na aba "Arquivos alterados" da página de pull request gerou o erro 404. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' + - 'Não foi possível adicionar usuários a uma organização ou excluir a organização após a remoção em massa de todos os usuários e administradores dessa organização. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' + - 'Os comentários de revisão em arquivos que contêm diacríticos e caracteres não latinos no nome do arquivo na página "Arquivos alterados" desapareceram quando a página foi recarregada. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'O estado da caixa de seleção "Visualizado" não foi mantido para arquivos que contêm diacríticos e caracteres não latinos no nome do arquivo na página "Arquivos alterados". {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'Os pulls requests mostraram o selo "Aprovado" quando nem todas as revisões necessárias estavam em vigor. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' + - 'O menu suspenso de tags estava vazio ao procurar uma tag em repositórios com mais de 100 tags. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' + - 'As páginas de pull request que mostram anotações com títulos diferentes de UTF-8 puderam encontrar erros de codificação na representação da vista. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' + - 'Uma condição de corrida para atualização na página OAuth pode fazer com que um redirecionamento seja executado duas vezes. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' + - 'A página "Tokens de Acesso Pessoal" esgotaria o tempo se houvesse mais de 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' + - 'Os trabalhos de sincronização programados para usuários e equipes de LDAP puderam ser iniciados enquanto os trabalhos de sincornização programados anteriormente ainda se encontram em processo. Implementou-se um mecanismo de bloqueio para evitar que os novos trabalhos de sincronização começassem, caso um deles ainda estivesse sendo executado. {% 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: - - 'The web notifications interface, including new [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) and [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) have been updated. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - - 'It is now possible to disable reactivation of LDAP users on LDAP sync. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' - - 'The push protected branch wording has been updated to clarify that admins can always push and that users with the Maintain role can push when status checks pass. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' - - 'Prevent blank commit when suggestion is identical to original text. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' - - 'Pagination is supported as a way to get more files in the diff associated with a commit via the REST API. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' - - 'Admins can enable, disable, delete, and search for webhooks using the webhook ID from the command line using `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' - - 'Automatic base retargeting will happen after manual head reference cleanup for a merged pull request. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' - - 'SVG files are handled as text and as images in the diff viewer. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' - - 'The "auto delete branches on merge" setting can be set when creating and updating repositories using the REST API. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' - - 'A new endpoint has been added to delete a deployment through the REST API. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' - - 'Admins can [enable security alerts](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) but disable all notifications from those alerts. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' - - 'The Pages log shows the user login accessing the GitHub Pages site. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' - - 'Enterprise members can see all of the organizations they belong to as part of their Enterprise account from one view by navigating to `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' - - '[REST API support for triage and maintain roles](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) has been expanded. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' - - 'A user can create and share search queries that resolve to the current user by using the `@me` search syntax. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' - - 'New issue template configuration options have been [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' - - 'MySQL backup and restore reliability and time to completion has been improved. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' - - '[Improved visibility](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) of pull requests and issue references in the issue sidebar, issue cards and issue list. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' - - 'Users can filter and search by `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' - - 'Automatic failover of MySQL within a single region for Cluster deployments is now possible. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' - - 'A user can compare tags between two releases to determine what changes have been made on the releases page. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' - - 'Outdated comments are no longer collapsed by default on the Pull Request timeline. They can be collapsed by resolving the thread. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' - - 'Admins can view a list of logins reserved for internal use by navigating to the "Reserved logins" stafftools tab. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' + - 'A interface de notificações web foi atualizada, incluindo [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) e [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) novos. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Agora é possível desabilitar a reativação de usuários de LDAP na sincronização de LDAP. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' + - 'A redação de *branch* protegido por push foi atualizada para esclarecer que os administradores podem sempre fazer envio por push e que os usuários com a função de Manutenção podem fazer push quando as verificações de status passarem. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' + - 'Evitar commit em branco quando a sugestão for idêntica ao texto original. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' + - 'A paginação é compatível como uma forma de obter mais arquivos no diff associados a um commit por meio da API REST. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' + - 'Administradores podem habilitar, desabilitar, excluir e pesquisar webhooks usando o ID do webhook na linha de comando e usando `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' + - 'Redirecionamento automático de base acontecerá após a limpeza manual de referência de cabeça para um pull request mesclado. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' + - 'Os arquivos SVG são tratados como texto e como imagens no visualizador de diff. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' + - 'A configuração "excluir branches automaticamente ao fazer merge" pode ser definida ao criar e atualizar repositórios usando a API REST. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' + - 'Um novo ponto de extremidade foi adicionado para excluir uma implantação por meio da API REST. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' + - 'Os administradores podem [habilitar alertas de segurança](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) e desabilitar todas as notificações desses alertas. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' + - 'O registro de Pages mostra o login do usuário que está acessando o site do GitHub Pages. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' + - 'Os integrantes corporativos podem ver todas as organizações às quais pertencem como parte da sua conta empresarial em apenas uma visualização, acessando `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' + - '[Suporte da API REST para triagem e manutenção de funções](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) foi expandido. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' + - 'Um usuário pode criar e compartilhar consultas de pesquisa que resolvam para o usuário atual se utilizar a sintaxe de pesquisa `@me`. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' + - 'Novas opções de configuração de modelo de problema foram [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' + - 'O backup e restauração de confiabilidade e tempo para a conclusão do MySQL foram aprimorados. {% comment %} https://github.com/github/ghes-infrare/issues/162 {% endcomment %}' + - '[Visibilidade aprimorada](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) de pull requests e referências de problemas na barra lateral de problemas, cartões de problemas e lista de problemas. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - 'Os usuários podem filtrar e pesquisar por `linked:pr` ou `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' + - 'Agora é possível a recuperação automática de falhas de MySQL dentro de apenas uma região de implantações de Cluster. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' + - 'Um usuário pode comparar tags entre duas versões para determinar quais alterações foram feitas na página de versões. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' + - 'Comentários desatualizados não são mais recolhidos por padrão na linha do tempo do Pull Request. Eles podem ser recolhidos resolvendo o tópico. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' + - 'Os administradores podem ver uma lista de logins reservados para uso interno, acessando para a aba de ferramentas de equipe "Reservadas". {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'Ao fazer push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% 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 push em um repositório na linha de comando. (atualizado 2020-06-23) {% 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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/1.yml b/translations/pt-BR/data/release-notes/2-21/1.yml index 09c1fed908..707471b775 100644 --- a/translations/pt-BR/data/release-notes/2-21/1.yml +++ b/translations/pt-BR/data/release-notes/2-21/1.yml @@ -10,10 +10,10 @@ sections: - 'A política da conta corporativa "Exclusão de problema do repositório" não refletiu a configuração salva no momento. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' - 'O log de auditoria não incluiu eventos de alteração de proteção de branch. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/10.yml b/translations/pt-BR/data/release-notes/2-21/10.yml index 95d45c5286..913683d235 100644 --- a/translations/pt-BR/data/release-notes/2-21/10.yml +++ b/translations/pt-BR/data/release-notes/2-21/10.yml @@ -5,10 +5,10 @@ sections: bugs: - 'A mensagem da conta corporativa "Confirmar requisito de dois fatores" estava incorreta. {% comment %} https://github.com/github/github/pull/158736 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/11.yml b/translations/pt-BR/data/release-notes/2-21/11.yml index 10708e361a..2e0e4a0f46 100644 --- a/translations/pt-BR/data/release-notes/2-21/11.yml +++ b/translations/pt-BR/data/release-notes/2-21/11.yml @@ -8,9 +8,9 @@ sections: - 'Editar templates de problemas com nomes de arquivos que contenham caracteres diferentes de ASCII gerariam uma falha com um "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' - 'Um método métrico de coleta em segundo plano para aumentar a utilização da CPU. (atualizado 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/12.yml b/translations/pt-BR/data/release-notes/2-21/12.yml index b394db5e4e..ac64ac8c15 100644 --- a/translations/pt-BR/data/release-notes/2-21/12.yml +++ b/translations/pt-BR/data/release-notes/2-21/12.yml @@ -7,9 +7,9 @@ sections: - 'Quando a política de "alteração de visibilidade do repositório" na conta corporativa foi definida como "Habilitada", os proprietários da organização não conseguiram alterar a visibilidade dos repositórios na organização. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 em vez do endereço IP da fonte real. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/13.yml b/translations/pt-BR/data/release-notes/2-21/13.yml index 8d5fc176e7..991a21b794 100644 --- a/translations/pt-BR/data/release-notes/2-21/13.yml +++ b/translations/pt-BR/data/release-notes/2-21/13.yml @@ -10,9 +10,9 @@ sections: - 'A sincronização de pull request em repositórios com muitas referências pode fazer com que as filas de trabalhador sejam atrasadas. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' - 'Ao efetuar o login após tentar visitar uma página específica, as pessoas eram enviadas para a página inicial em vez de serem enviadas para o seu destino pretendido. {% 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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/14.yml b/translations/pt-BR/data/release-notes/2-21/14.yml index 937f171c22..d62558dbb0 100644 --- a/translations/pt-BR/data/release-notes/2-21/14.yml +++ b/translations/pt-BR/data/release-notes/2-21/14.yml @@ -4,9 +4,9 @@ sections: - '**BAIXO:** Alto uso da CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN, o que resulta em em Negação de Serviço (DoS). {% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/2.yml b/translations/pt-BR/data/release-notes/2-21/2.yml index da587a3cfe..20259bd150 100644 --- a/translations/pt-BR/data/release-notes/2-21/2.yml +++ b/translations/pt-BR/data/release-notes/2-21/2.yml @@ -10,10 +10,10 @@ sections: - 'A VPN entre nós pode tornar-se instável, fazendo com que erros sejam registrados e espaço livre no volume raiz seja esgotado. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' - 'Os repositórios internos não foram incluídos corretamente nos resultados de pesquisa para as orgs habilitadas com SAML. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/3.yml b/translations/pt-BR/data/release-notes/2-21/3.yml index a0ef24b138..708feac308 100644 --- a/translations/pt-BR/data/release-notes/2-21/3.yml +++ b/translations/pt-BR/data/release-notes/2-21/3.yml @@ -7,10 +7,10 @@ sections: - 'Não era possível usar o fluxo de criação do manifesto do aplicativo GitHub em alguns cenários quando uma política de Cookie do SameSite foi aplicada. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' - 'Em algumas circunstâncias, o acesso à página de "Explorar" geraria um erro no aplicativo. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/4.yml b/translations/pt-BR/data/release-notes/2-21/4.yml index 998c3fd246..c7151b2741 100644 --- a/translations/pt-BR/data/release-notes/2-21/4.yml +++ b/translations/pt-BR/data/release-notes/2-21/4.yml @@ -10,17 +10,17 @@ sections: - 'A plataforma de virtualização para sistemas oVirt KVM não foi detectada corretamente, gerando problemas durante as atualizações. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - 'A mensagem de erro para autenticação inválida com uma senha via linha de comando do Git não preencheu a URL vinculada à adição do token apropriado ou chave SSH. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}' - 'Criar um problema em um repositório de usuário que usa o recurso de modelo do problema pode falhar com um erro de servidor interno. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' - - 'Visiting the *Explore* section failed with a 500 Internal Server error. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' - - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' - - 'Internal metrics gathering for background jobs contributed to CPU and memory use unnecessarily. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' - - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' - - 'Background jobs for an unreleased feature were queued and left unprocessed. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' + - 'Ocorreu uma falha ao acessar a seção *Explorar* com um erro de servidor interno de 500. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' + - 'Os problemas não puderam ser classificados por *Atualizações recentes* nos repositórios migrados para uma nova instância. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/github/pull/149330 {% endcomment %}' + - 'O GitHub Connect estava usando um ponto obsoleto da API do GitHub.com. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'A coleta de métricas internas para trabalhos de segundo plano contribuiu para o uso desnecessário da CPU e da memória. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' + - 'A página 404 continha links de contato e links status do GitHub.com na nota de rodapé. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' + - 'Trabalhos de segundo plano para um recurso não publicado foram enfileirados e deixados sem processamento. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/5.yml b/translations/pt-BR/data/release-notes/2-21/5.yml index 57da462c18..22a1122a48 100644 --- a/translations/pt-BR/data/release-notes/2-21/5.yml +++ b/translations/pt-BR/data/release-notes/2-21/5.yml @@ -5,10 +5,10 @@ sections: - 'Alterações recentes nas alocações de memória podem gerar uma degradação no desempenho do sistema {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' - 'Problemas temporários de conectividade durante a execução de migrações de banco de dados podem gerar perda de dados. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/7.yml b/translations/pt-BR/data/release-notes/2-21/7.yml index 5ca05349fe..6448ee9f5f 100644 --- a/translations/pt-BR/data/release-notes/2-21/7.yml +++ b/translations/pt-BR/data/release-notes/2-21/7.yml @@ -4,10 +4,10 @@ sections: - 'Uma verificação de saúde do serviço causou o crescimento da sessão, o que gerou um esgotamento do sistema de arquivos. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - 'A atualização que usa um hotpatch pode falhar com um erro: `''libdbi1'' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/8.yml b/translations/pt-BR/data/release-notes/2-21/8.yml index bf155ba240..13afccece3 100644 --- a/translations/pt-BR/data/release-notes/2-21/8.yml +++ b/translations/pt-BR/data/release-notes/2-21/8.yml @@ -6,10 +6,10 @@ sections: bugs: - 'Os administradores não conseguiram ver webhooks de repositório entregues e, ao invés disso, viram "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-21/9.yml b/translations/pt-BR/data/release-notes/2-21/9.yml index e459d81edd..f909cb0399 100644 --- a/translations/pt-BR/data/release-notes/2-21/9.yml +++ b/translations/pt-BR/data/release-notes/2-21/9.yml @@ -19,10 +19,10 @@ sections: - 'Remova o requisito de impressões digitais SSH nos arquivos "ghe-migrator", pois ele sempre pode ser computado. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' - 'Os manifestos do aplicativo GitHub agora incluem o 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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-22/0.yml b/translations/pt-BR/data/release-notes/2-22/0.yml index 602ee375fe..a5027bfb19 100644 --- a/translations/pt-BR/data/release-notes/2-22/0.yml +++ b/translations/pt-BR/data/release-notes/2-22/0.yml @@ -5,21 +5,21 @@ sections: - heading: GitHub Actions Beta notes: - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + [GitHub Actions](https://github.com/features/actions) é uma solução poderosa e flexível para CI/CD e automação de fluxo de trabalho. O GitHub Actions no Enterprise Server inclui ferramentas que ajudam você a gerenciar o serviço incluindo métricas chave no Console de Gerenciamento, logs de auditoria e controles de acesso para ajudar você a controlar a implementação. - You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} + Você precisará fornecer seu próprio [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) e executores para o GitHub Actions. AWS S3, Azure Blob Storage e MinIO são compatíveis. Revise os [requisitos mínimos atualizados para sua plataforma](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) antes de ativar o GitHub Actions. Para saber mais, entre em contato com a equipe do GitHub Sales ou [inscreva-se para o 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) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + [GitHub Packages](https://github.com/features/packages) é um serviço de hospedagem de pacotes, integrado nativamente com as APIs, ações e webhooks do GitHub. Crie um [fluxo de trabalho de ponta a ponta para o DevOps](https://docs.github.com/en/enterprise/2. 2/admin/pacotes/configuring-packages-support-for-your-enterpris) que inclui seu código, integração contínua e soluções de implantação. - 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](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} + Os backends de armazenamento compatíveis incluem AWS S3 e MinIO com suporte para o Azure blob em uma versão futura. Observe que o suporte atual ao Docker será substituído por uma versão beta do novo Registro de Contêiner do GitHub na próxima versão. Revise os [requisitos mínimos atualizados para sua plataforma](https://docs.github.com/en/enterprise/2. 2/admin/installation/setting-up-a-github-enterprise-server-instance) antes de ativar o GitHub Packages. Para saber mais, entre em contato com a equipe do GitHub Sales ou [inscreva-se no beta](https://resources. ithub.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} - heading: Varredura avançada de segurança de código beta notes: - | - [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. + [Varredura avançada de código de segurança do GitHub](https://github.com/features/security) é um ambiente de teste de segurança para aplicativos estáticos nativos do GitHub nativo (SAST). Encontre facilmente vulnerabilidades de segurança antes que atinjam a produção, tudo desenvolvido pelo mais poderoso motor de análise de código do mundo: CodeQL. - Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} + Os administradores que usam a Segurança Avançada do GitHub podem [inscrever-se em](https://resources.github.com/beta-signup/) e [enable](https://docs.github. om/pt/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) o Beta de varredura avançada de código de segurança GitHub. Revise os [requisitos mínimos atualizados para sua plataforma](https://docs.github. om/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) antes de ativar a varredura avançada de código código de segurança GitHub. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} - heading: Redirecionamento de pull request notes: - | @@ -31,9 +31,9 @@ sections: - heading: Desempenho aprimorado em grande escala notes: - | - We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% 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 %}'' + Nós revisamos a abordagem que adotamos para agendar a manutenção da rede para repositórios, garantindo que os grandes monorrepositórios sejam capazes de evitar os estados de falha. {% comment %} https://github.com/github/github/pull/146789, https://github.com/github/github/pull/147931, https://github.com/github/github/pull/146724, https://github. om/github/git-protocols/issues/94 {% endcomment %}'' - Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} + As réplicas passivas agora são [compatíveis e configuráveis nas implantações de cluster do GitHub Enterprise Server](https://docs.github.com/en/enterprise/2. 2/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). Essas alterações permitirão falhas mais rápidas, reduzindo RTO e RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} - heading: Visualizar todos os seus usuários notes: - | @@ -42,30 +42,30 @@ sections: - heading: Alterações na administração notes: - 'Os trabalhadores compartilhados foram habilitados para tornar as atualizações ao vivo mais resilientes, compartilhando conexões entre as abas. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %}' - - 'The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %}' - - 'It''s now possible to [manage global announcements and expiration dates through the enterprise account settings](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 %}' - - 'You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %}' - - 'Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository''s settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %}' - - 'A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% 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 %}' - - 'The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %}' - - 'The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %}' - - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% 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: Security Changes + - 'O link "Suporte ao Contato" na página de erro `50x` agora vincula ao e-mail de suporte ou link configurado no Console de Gerenciamento. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %}' + - 'Agora é possível [gerenciar anúncios e datas de expiração globais pelas configurações da conta corporativa](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/pull/148475, https://github.com/github/github/pull/148494 {% endcomment %}' + - 'Agora você pode [isentar certos usuários do limite de taxa da API padrão configurado no console de gerenciamento](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), se necessário. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %}' + - 'Agora os administradores do repositório podem [definir seus repositórios como qualquer opção de visibilidade disponível](https://docs.github.com/en/enterprise/2.22/user/administering-a-repository/setting-repository-visibility) a partir de um único diálogo nas configurações do repositório. Anteriormente, você tinha de navegar por seções, botões e caixas de diálogo separadas para alternar entre público e privado e entre privado e interno. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %}' + - 'Um novo link de configurações corporativasno menu suspenso do usuário facilita a navegação nas Configurações da Conta Corporativa. {% 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 %}' + - 'O antigo link "Central de Adminstraão" na página de /stafftools foi removido. O link "Empresa" agora é a melhor maneira de acessar a Conta Corporativa a partir da página /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %}' + - 'O item do submenu de Opções nas configurações da Conta Corporativa foi transferido da seção de Configurações para a seção de Políticas. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %}' + - '[Acessar recursos usando um token de acesso pessoal ou chave SSH agora conta como atividade de usuário](https://docs.github.com/en/enterprise/2.22/admin/user-management/management/managing-dormant-users). Isso alivia os administradores do trabalho de filtrar determinados usuários dos relatórios de dormência do usuário e torna mais seguro usar o botão "Suspender todos" sem suspender, acidentalmente, usuários que acessaram o GitHub de forma apenas leitura através das APIs com um Token de Acesso Pessoal (PAT) ou chave 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: Alterações de segurança notes: - - 'Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %}' - - 'When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](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 %}' - - 'Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %}' - - heading: Developer Changes + - 'Os códigos de recuperação de dois fatores não podem mais ser usados durante o processo de autenticação de dois fatores. As senhas de uso único são os únicos valores aceitáveis. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %}' + - 'Quando um usuário é conectado ao GitHub Enterprise Server através de um único logon, a [seleção de visibilidade padrão do repositório é 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 %}' + - 'Agora os proprietários dos aplicativos GitHub podem escolher que os seus [tokens de acesso do usuário para servidor expirem após 8 horas](https://developer.github. om/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), para ajudar a aplicar rotação regular do token e reduzir o impacto de um token comprometido. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %}' + - heading: Alterações de desenvolvedor notes: - - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' - - 'In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %}' - - 'Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' - - 'Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %}' + - '[A interface de usuário do GitHub passou por uma atualização de design](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), e a página inicial dos repositórios foi reprojetada, incluindo um layout responsivo e uma melhor experiência de web móvel. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' + - 'No menu suspenso do repositório "Clonar com SSH", os usuários agora serão notificados se não tiverem nenhuma configuração de chaves. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %}' + - 'Agora, os commits são ordenados cronologicamente na linha do tempo do pull request e na aba commits. Esta nova ordem também é refletida na API REST de ["Lista de commits em um pull request"](https://docs.github.com/en/enterprise/2. 2/user/rest/reference/pulls#list-commits-on-a-pull-request) e no [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 %}' + - 'Agora os usuários podem [definir o padrão do tom de tema padrão para resultados de preenchimento automático de emojis](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) nas áreas de texto de comentário. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %}' - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' - - heading: Users and organizations can add Twitter usernames to their GitHub profiles + - heading: Os usuários e as organizações podem adicionar nomes de usuários do Twitter aos seus perfis do GitHub notes: - '[Developers and organizations can now add their Twitter username to their profile](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: API Changes + - heading: Alterações de API notes: - | #### Graduated Previews @@ -93,8 +93,8 @@ sections: - 'The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %}' - 'The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %}' - 'A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %}' - - 'If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner''s "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %}' - - 'Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %}' + - 'Se um usuário acessar um repositório cujo nome foi iniciado com "repositórios", ele será direcionado a aba "Repositórios" do proprietário em vez de chegar à página de visão geral do repositório. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %}' + - 'As etiquetas na linha do tempo do painel não têm contraste suficiente. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %}' deprecations: - heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 notes: @@ -111,9 +111,9 @@ sections: backups: - 'GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/).' 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - 'The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %}' @@ -122,4 +122,4 @@ sections: - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a 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 %}' - 'GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %}' - 'On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization''s dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% 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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-22/1.yml b/translations/pt-BR/data/release-notes/2-22/1.yml index dbc5b4fd91..2027104a6f 100644 --- a/translations/pt-BR/data/release-notes/2-22/1.yml +++ b/translations/pt-BR/data/release-notes/2-22/1.yml @@ -51,20 +51,20 @@ sections: - | Quando um grande número de resultados de verificação de código foi enviado ao mesmo tempo, o tempo de processamento de lotes pode expirar, gerando uma parada no processamento dos resultados de varredura do código. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} - | - [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} + [Criar um aplicativo GitHub a partir de um manifesto](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) falhará. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} - | - GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management Console. {% comment %} https://github.com/github/github/pull/158131, https://github.com/github/github/pull/157936, https://github.com/github/external-identities/issues/335 {% endcomment %} + O nomes de usuário do GitHub foram alterados involuntariamente ao usar a autenticação do SAML, quando o nome de usuário do GitHub não correspondeu ao valor do atributo mapeado com o campo `username` no Console. {% 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: - 'O suporte é adicionado ao tipo de instância do AWS EC2 `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - 'Remova o requisito de impressões digitais SSH nos arquivos "ghe-migrator", pois ele sempre pode ser computado. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %}' - 'Os manifestos do aplicativo GitHub agora incluem o 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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - 'Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %}' - - 'GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' - - 'On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization''s dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% 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 %}' + - 'As atualizações de configuração irão falhar ao restaurar os dados para uma instância habilitada pelo GitHub Actions se a fonte original de backup não tiver o recurso habilitado. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %}' + - 'O GitHub Actions pode falhar ao iniciar com sucesso se estiver previamente habilitado em uma instância com versão 2.22.0 e for atualizado para 2.22.1. (atualizado 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' + - 'Em uma instância nova com a configuração 2.22.1 ou após a atualização para 2.22.1, o feed de atividades no painel de uma organização não será mais atualizado. (atualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-22/2.yml b/translations/pt-BR/data/release-notes/2-22/2.yml index 1d7a3fa944..54eebb54c5 100644 --- a/translations/pt-BR/data/release-notes/2-22/2.yml +++ b/translations/pt-BR/data/release-notes/2-22/2.yml @@ -1,28 +1,28 @@ date: '2020-10-20' sections: security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' bugs: - | - If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} + Se as configurações da conta de armazenamento não conseguiram validar ao configurar as ações do GitHub, a execução de `ghe-actions-teardown` foi necessária antes de fazer uma nova tentativa. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} - | - A custom proxy configuration could adversely affect the GitHub Actions environment. {% 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 %} + Uma configuração de proxy personalizada pode afetar negativamente o ambiente do 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 %} - | - On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} + Em uma mudança de endereço no eth0, o Nomad e o Cônsul poderiam ficar sem resposta. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} - | - When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} + Ao usar certificados autosassinados, o GHES pode ter exceções de validação SSL na configuração do GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} - | - Using a GitHub Action from a branch name with a `+` or `/` character resulted in an 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 %} + O uso de uma ação do GitHub de um branch com um caractere `+` ou `/` gerou um erro: `Unable to resolve action`. {% comment %} https://github. om/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} - | - The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} + A mensagem da conta corporativa "Confirmar requisito de dois fatores" estava incorreta. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} - | - On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} + Em certas solicitações acima de 100 MB, o buffer de Kafka pode ser sobre-alocado. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' - - 'GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' - - 'On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization''s dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% 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 %}' + - 'O GitHub Actions pode falhar ao iniciar com sucesso se estiver previamente habilitado em uma instância com versão 2.22.0 e for atualizado para 2.22.2. (atualizado 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' + - 'Em uma instância nova com a configuração 2.22.2 ou após a atualização para 2.22.2, o feed de atividades no painel de uma organização não será mais atualizado. (atualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% 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 %}' diff --git a/translations/pt-BR/data/release-notes/2-22/3.yml b/translations/pt-BR/data/release-notes/2-22/3.yml index ed2b038671..d6edd0056a 100644 --- a/translations/pt-BR/data/release-notes/2-22/3.yml +++ b/translations/pt-BR/data/release-notes/2-22/3.yml @@ -2,21 +2,21 @@ date: '2020-11-03' sections: security_fixes: - | - **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} + **BAIXO:** O alto uso da CPU pode ser acionado por uma solicitação especialmente elaborada para a ponte SVN, gerando Negação de Serviço (DoS) no serviço da ponte SVN. (atualizado 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} - | **BAIXO:** A validação incorreta de token gerou uma entropia reduzida para os tokens de correspondência durante a autenticação. A análise mostra que, na prática, não há risco significativo de segurança aqui. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} - | Os pacotes foram atualizados para as últimas versões de segurança. {% 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: - - 'GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 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 %}' + - 'O GitHub Actions pode falhar ao iniciar com êxito caso tenha sido habilitado previamente em uma instância com execução 2.22.0 e caso tenha sido atualizado para a 2.22.1 ou 2.22.2 {% comment %} https://github. om/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' - 'Os arquivos de configuração para o GitHub Actions não foram copiados para a réplica ao configurar as réplicas de alta disponibilidade, gerando, potencialmente erros durante `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %}' - - 'On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization''s dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %}' + - 'Em uma nova instância com a configuração 2.22.1 ou 2.22.2 ou após a atualização para 2.22.1 ou 2.22.2, o feed de atividades no painel de uma organização não seria atualizado. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %}' - 'Editar templates de problemas com nomes de arquivos que contenham caracteres diferentes de ASCII gerariam uma falha com um "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %}' - 'Um método métrico de coleta em segundo plano para aumentar a utilização da CPU. (atualizado 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP da fonte real. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-22/4.yml b/translations/pt-BR/data/release-notes/2-22/4.yml index ad176a9e83..3458c0e073 100644 --- a/translations/pt-BR/data/release-notes/2-22/4.yml +++ b/translations/pt-BR/data/release-notes/2-22/4.yml @@ -8,8 +8,8 @@ sections: - 'Quando a política de "alteração de visibilidade do repositório" na conta corporativa foi definida como "Habilitada", os proprietários da organização não conseguiram alterar a visibilidade dos repositórios na organização. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %}' - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 em vez do endereço IP da fonte real. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-22/5.yml b/translations/pt-BR/data/release-notes/2-22/5.yml index ecd318d528..012ff5e534 100644 --- a/translations/pt-BR/data/release-notes/2-22/5.yml +++ b/translations/pt-BR/data/release-notes/2-22/5.yml @@ -14,8 +14,8 @@ sections: - 'Ao efetuar o login após tentar visitar uma página específica, as pessoas eram enviadas para a página inicial em vez de serem enviadas para o seu destino pretendido. {% 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 instâncias de GHES que usam autenticação integrada com um provedor de identidade do SAML interno, os usuários sem um endereço de e-mail associado não podem criar um commit a partir da interface 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: - - '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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/2-22/6.yml b/translations/pt-BR/data/release-notes/2-22/6.yml index eccedd90f4..fa62449e96 100644 --- a/translations/pt-BR/data/release-notes/2-22/6.yml +++ b/translations/pt-BR/data/release-notes/2-22/6.yml @@ -5,13 +5,13 @@ sections: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/24353, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' bugs: - 'As solicitações de alguns recursos de arquivo como um arquivo zip ou um arquivo não processado podem entrar em um loop de redirecionamento. {% comment %} https://github.com/github/enterprise2/pull/24193, https://github.com/github/enterprise2/pull/24075 {% endcomment %}' - - 'A timeout could prevent some Issues and Pull Requests searches from providing complete search results. {% comment %} https://github.com/github/github/pull/164155, https://github.com/github/github/pull/163845 {% endcomment %}' - - 'Custom tabs with non-alphabetic characters in small screens did not render correctly. {% comment %} https://github.com/github/github/pull/164310, https://github.com/github/github/pull/164159 {% endcomment %}' - - 'An underlying behavior was causing failures when pushing content to a Git LFS-enabled repository. {% comment %} https://github.com/github/github/pull/164663, https://github.com/github/github/pull/150179 {% endcomment %}' - - 'In some rare cases issues could cause a 500 error when accessed via the web interface. {% comment %} https://github.com/github/github/pull/165298, https://github.com/github/github/pull/159674 {% endcomment %}' + - 'Um limite de tempo pode impedir que algumas pesquisas de problemas e pull requests forneçam resultados de pesquisa completos. {% comment %} https://github.com/github/github/pull/164155, https://github.com/github/github/pull/163845 {% endcomment %}' + - 'Abas personalizadas com caracteres não alfabéticos em telas pequenas não foram interpretadas corretamente. {% comment %} https://github.com/github/github/pull/164310, https://github.com/github/github/pull/164159 {% endcomment %}' + - 'Um comportamento subjacente estava causando falhas ao fazer push de conteúdo em um repositório do Git habilitado com LFS. {% comment %} https://github.com/github/github/pull/164663, https://github.com/github/github/pull/150179 {% endcomment %}' + - 'Em alguns casos raros, os problemas podem gerar um erro 500 quando acessados pela interface web. {% comment %} https://github.com/github/github/pull/165298, https://github.com/github/github/pull/159674 {% 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 %}' + - '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 %}' - - '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 %}' + - '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 %}' diff --git a/translations/pt-BR/data/release-notes/3-0/0-rc1.yml b/translations/pt-BR/data/release-notes/3-0/0-rc1.yml index f1a0683507..1b298de85b 100644 --- a/translations/pt-BR/data/release-notes/3-0/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/3-0/0-rc1.yml @@ -1,145 +1,145 @@ --- date: '2021-01-12' release_candidate: true -intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)". +intro: As versões de candidatos devem ser testadas em ambientes que não são de produção. Para obter mais informações sobre o Programa Candidato de Versão, consulte o [Blogue do GitHub](https://github. log/2020-12-03-improving-the-ghes-release-process-release-candidates/) ou "[Sobre atualizações de novas versões](/admin/overview/about-upgrades-to-new-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. + [{% data variables.product.prodname_actions %}] (https://github.com/features/actions) está disponível em {% data variables.product.prodname_ghe_server %} 3,0+. Crie, teste e implante seu código a partir de {% data variables.product.prodname_dotcom %}. Envie revisões de código, gerenciamento de branches e triagem de problemas da maneira que você desejar. - This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: + Esta versão inclui várias melhorias da versão beta de {% data variables.product.prodname_actions %} em {% 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. + - Os administradores corporativos, de organização e repositório podem criar políticas de segurança para acessar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_dotcom_the_website %}. + - Os administradores corporativos, de organização e repositórios podem permitir que os repositórios públicos usem executores auto-hospedados. + - Os administradores corporativos, de organização e repositórios agora podem permitir que os fluxos de trabalho sejam [executados em pull requests abertos em bifurcações de repositórios privados](/enterprise-server@3.0/github/configuração-e-gerenciamento-organizações-e-equipes/desativar-ou-limitar-github-actions-for-your-organization#enableing-workflows-for-private-repositório-forks). + - O evento 'workflow_run' é [agora compatível](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) + - Agora, os usuários agora têm a capacidade de [desabilitar os fluxos de trabalho e habilitá-los posteriormente](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enableing-a-workflow). + - Os registros do fluxo de trabalho foram aprimorados para uma [melhor experiência do usuário](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). + - Os usuários agora podem usar imagens privadas em trabalhos e serviços de contêineres. + - Os dias máximos de retenção para [artefatos e registros agora podem ser personalizados](/enterprise-server@3.0/github/configuração-e-gerenciamento-sua-empresa/configuração-o-período de retenção-para-github-ações-artefatos-e-logs-em-sua-conta corporativa). + - A API do grupo do executor agora inclui [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). + - Agora você pode criar ações reutilizáveis usando scripts shell com etapas de execução de composição. + - [Segredos criptografados para uma organização](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) permitem que você consolide segredos em repositórios. + - [Modelos de fluxo de trabalho para uma organização](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) simplifica e promove as práticas recomendadas e a consistência em toda a sua organização. - {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. + {% data variables.product.prodname_actions %} não é atualmente compatível para empresas que usam configurações de cluster. - heading: GitHub Package Registry 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. + [{% data variables.product.prodname_registry %}](https://github.com/features/packages) é um serviço de hospedagem de pacotes, integrado nativamente às APIs, ações e webhooks do GitHub. Crie um [fluxo de trabalho de DevOps de ponta a ponta](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterpris-enterprise) que inclui o seu código, integração contínua e soluções de implantação. - 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 %}. + Os backends de armazenamento compatíveis incluem AWS S3 e MinIO com suporte para o Azure blob que virá em uma versão futura. Observe que o suporte atual do Docker será substituído por uma versão beta do novo GitHub Container Registry na próxima versão. Revise os requisitos mínimos [atualizados para sua plataforma](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) antes de ativar {% 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) + Ao publicar pacotes no NuGet, os usuários agora podem usar a opção `--api-key` para passar seu token de autenticação em vez de escrevê-lo em um arquivo. Para obter mais informações, consulte [Configurar CLI do dotnet para uso com o 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. + {% data variables.product.prodname_registry %} não é atualmente compatível para empresas que usam configurações de cluster. - 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 %}. + O beta de [{% data variables.product.prodname_mobile %}](https://github.com/features/) permite que você faça triagem de notificações e gerencie problemas e pull requests a partir do seu dispositivo. Você pode estar conectado simultaneamente ao celular com uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %} e uma conta de usuário em {% 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`. + O beta de {% data variables.product.prodname_mobile %} agora está disponível para {% data variables.product.prodname_ghe_server %}. Efetue o login com os nossos aplicativos [Android](https://play.google.com/store/apps/details?id=com.github.android) e [iOS](https://apps.apple.com/app/github/id1477376905) para monitorar notificações e gerenciar problemas e pull requests em qualquer lugar. Os administradores podem desabilitar o suporte móvel para a sua Empresa usando o console de gerenciamento ou executando o comando `ghe-config app.mobile.enabled false`. - - heading: Advanced Security Secret Scanning beta + heading: Beta de varredura de segredo de segurança avançada 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. + [Varredura de segredo beta](https://github. um/recursos/segurança) faz a varredura de repositórios públicos e privados com relação a credenciais comprometidas, encontra segredos, e notifica o provedor do segredo ou administrador no momento em que são autorizados em um repositório. - 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. + Os administradores que usam {% data variables.product.prodname_GH_advanced_security %} podem [habilitar e configurar](/enterprise-server@3. /admin/configuration/configuring-secret-scanning-for-your-appliance) a varredura de segredo de {% data variables.product.prodname_GH_advanced_security %}. Você pode revisar os [requisitos mínimos atualizados para sua plataforma](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) antes de habilitar a varredura de segredo de {% data variables.product.prodname_GH_advanced_security %}. - - heading: Advanced Security Code Scanning + heading: Varredura Avançada de Código de Segurança 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)" + [A Varredura Avançada de Código de Segurança do GitHub](https://github.com/features/security) agora está geralmente disponível no GitHub Enterprise Server. As organizações que adquiriram Segurança Avançada podem usar este recurso para fazer testes de segurança de análise estática com seu código e evitar que vulnerabilidades cheguem ao código de produção usando CodeQL, o nosso mecanismo de análise semântica. Para obter mais informações, consulte "[Configurar a varredura de código no seu aplicativo](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" changes: - heading: Alterações na administração 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. + - O sistema de entrega de eventos de webhook foi rearquitetado para rendimentos mais altos, entregas mais rápidas e menor atraso nas mensagens de erro.. Além disso, ele usa menos CPU e memória em {% data variables.product.prodname_ghe_server %} 3.0+. + - Os proprietários da organização e da empresa agora podem ver quando um integrante da equipe foi promovido ou rebaixado de ser um mantenedor de equipe no log de auditoria por meio os novos eventos de log de auditoria `team.promote_maintainer` e `team.demote_maintainer`. Para obter mais informações, consulte "[Ações auditadas](/enterprise-server@3.0/admin/user-management/audited-actions)." + - 'Os mantenedores do repositório com os sites de {% data variables.product.prodname_pages %} existentes podem [atualizar facilmente o nome padrão anterior do branch](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' + - São necessários recursos adicionais de hardware para executar {% data variables.product.prodname_ghe_server %} com qualquer uma das Ações, Pacotes ou Segurança Avançada habilitadas. Para obter mais informações sobre os recursos mínimos necessários para cada plataforma compatível, consulte "[Configurar uma instância de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Agora os administradores podem [publicar uma mensagem](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), que todos os usuários devem aceitar. Isso pode ajudar a integrar novos usuários e supervisionar outras informações e políticas específicas da organização. - - heading: Security Changes + heading: Alterações de segurança 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. + - Os proprietários da organização agora podem desabilitar a publicação de sites de {% data variables.product.prodname_pages %} dos repositórios na organização. Desabilitar {% data variables.product.prodname_pages %} para a organização impedirá que os integrantes criem novos sites de páginas, mas não irá cancelar a publicação de sites existentes. Para obter mais informações, consulte "[Desabilitar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." + - Um centro de dados deve ser definido explicitamente em todos os nós antes de habilitar uma réplica ativa. + - Todo o uso de impressões digitais de SSH foi alterado para usar as impressões digitais de SHA256, pois são usadas com o OpenSSH desde a versão 6.8. Isto se aplica à interface web e também à API em que as impressões digitais são retornadas, como no GraphQL. As impressões digitais seguem o formato OpenSSH. + - Os cabeçalhos de assinatura SHA-1 e SHA-256 (dois cabeçalhos) são enviados em webhooks. - - heading: Developer Changes + heading: Alterações de desenvolvedor 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. + - A maioria dos serviços em execução em {% data variables.product.prodname_ghe_server %} 3.0 + estão agora nos contêineres, o que permite que o GitHub itere internamente e envie rapidamente versões de qualidade + - O sistema de entrega de eventos webhook foi rearquivado para melhor rendimento, entregas mais rápidas e menor atraso nas mensagens. - - heading: API Changes + heading: Alterações de 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)."' + - 'Os administradores agora podem configurar e gerenciar o anúncio do banner para todo o site através da API REST. Para obter mais informações, consulte os pontos de extremidade para "[Administração do GitHub Enterprise](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' - - heading: Default branch renaming + heading: Renomeação do branch padrão 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. + Os administradores da empresa e da organização agora podem definir o nome do branch padrão para novos repositórios. Os administradores das empresas também podem aplicar a sua escolha do nome do branch padrão em todas as organizações ou permitir que as organizações individuais escolham suas próprias. - Existing repositories are unaffected by these settings, and their default branch name will not be changed. + Os repositórios existentes não são afetados por essas configurações, e seu nome de branch padrão não será alterado. {% 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. + O branch padrão para repositórios recém-criados será definido como `main` no GHES 3., a menos que você opte por não definir a configuração do branch padrão no nível empresarial. {% 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). + Esta alteração é uma das muitas mudanças que o GitHub está realizando para ser compatível com projetos e mantenedores que desejam renomear seu branch padrão. Para saber mais sobre as mudanças que estamos criando, consulte [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. + - O formato de vários arquivos de registro foram alterados, incluindo a adição de um PID para diferentes tipos de registro. Isso não afeta como o Suporte GitHub Enterprise usa pacotes de suporte para solucionar problemas. + - Uma solicitação de PATCH para a API de configuração de webhook não apaga mais o segredo do webhook. deprecations: - - heading: Deprecation of GitHub Enterprise Server 2.19 + heading: Depreciação do 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.' + - '**{% data variables.product.prodname_ghe_server %} 2.19 estará obsoleto a partir de 12 de novembro de 2020**. Isso significa que não serão feitas versões de patch, mesmo para questões críticas de segurança, após esta data. Para obter um melhor desempenho, melhoria na segurança e novas funcionalidades, [atualize para a versão mais recente de {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) assim que possível.' - heading: Deprecation of Legacy GitHub App Webhook Events 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/). + - Começando com {% data variables.product.prodname_ghe_server %} 2.21.0, dois eventos legados de webhook relacionados a aplicativos GitHub foram descontinuados e serão removidos em {% data variables.product.prodname_ghe_server %} 3.2.0. Os eventos obsoletos `integration_installation` e `integration_installation_repositories` têm eventos equivalentes que serão compatíveis. Mais informações estão disponíveis no [post do blogue de anúncio de obsolescência](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). - heading: Deprecation of Legacy GitHub Apps Endpoint 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/). + - Começando com {% data variables.product.prodname_ghe_server %} 2.21, o ponto de extremidade do legado dos aplicativos GitHub para a criação de tokens de acesso de instalação foi suspenso e será removido em {% data variables.product.prodname_ghe_server %} 3.2.0. Mais informações estão disponíveis no [post do blogue de anúncio de depreciação](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). - heading: Deprecation of OAuth Application API 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/). + - O GitHub não é compatível mais com os pontos de extremidade do aplicativo OAuth que contêm `access_token` como um parâmetro de caminho. Nós introduzimos novos pontos de extremidade que permitem que você gerencie, com segurança, tokens para aplicativos OAuth movendo `access_token` para o texto da solicitação. Embora obsoleto, os pontos de extremidade ainda podem ser acessados nesta versão. Queremos remover esses pontos de extremidade em {% data variables.product.prodname_ghe_server %} 3.4. Para obter mais informações, consulte [post do blogue de anúncio de depreciação](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - - heading: Deprecation of support for Semiotic + heading: Depreciação de compatibilidade com o Semiotic notes: - - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. + - O serviço era compatível com uma experiência de "Encontrar por Símbolo" na vista de pull request que não era amplamente utilizada. - - heading: Deprecation of workflow commands + heading: Obsolescência de comandos de fluxo de trabalh 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/).' + - 'Os comandos do fluxo de trabalho `set-env` and `add-path` de {% data variables.product.prodname_actions %} tornaram-se obsoletos. Para obter mais informações, consulte o [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 release candidates in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. - - The image and upgrade package download size has increased. Customers on slow internet connections may find the packages take longer to download. + - 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. + - Candidato de Versão 1 não é compatível com o modo Cluster. + - As regras personalizadas de firewall não são mantidas durante uma atualização. + - Arquivos rastreados pelo LFS do Git [carregados por meio da interface web](https://github.blog/2016-02-18-upload-files-to-your-repositories/) foram adicionados incorreta e diretamente ao repositório. + - 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. + - Após uma tentativa mal sucedida de configurar ações, se você desabilitar as ações, você não poderá criar o primeiro usuário e usar o aplicativo + - O evento de log de auditoria "Mensagem obrigatória visualizada" não está sendo salvo + - '`ghe-config-apply` deve ser executado em uma réplica durante a primeira configuração antes de `ghe-repl-setup` poder ser executado para iniciar a replicação.' + - Os utilitários de backup podem acionar e-mails desnecessários para administradores + - As configurações incorretas de pacotes estão sendo exibidas na página de visualização dos integrantes da organização + - Após remover-se como um Proprietário da Empresa, você será redirecionado para uma página 404. A operação é bem-sucedida. + - 'Ocasionalmente, o `ghe-config-apply` falha com uma mensagem de `ERROR: Failure waiting for nomad jobs to apply` até que a fila de trabalho do Nomad seja esvaziada. De modo geral, isso exige que um administrador apague `/etc/nomad-jobs/queue`.' + - Ao configurar um nó de múltiplas réplicas, o status da réplica pode ser sincronizado incorretamente. + - Os clientes que tentarem restaurar um backup 3.0 em uma nova instância não deverão pré-configurar a instância, pois isso pode gerar um estado ruim para logins de usuário. Recomendamos restaurar uma instância nova e não configurada. + - Os candidatos da versão 3.0 do GitHub Enterprise Server ainda não estão disponíveis no marketplace do Azure. Para testar a versão de candidatos em ambientes de stage, inicie uma instância 2.21 ou 2.22 e, em seguida, atualize-a com o pacote de atualização do Azure na página de download. + - O tamanho da imagem e atualização do pacote aumentou. Os clientes com conexão lenta à internet podem achar que os pacotes demoram mais para serem baixados. 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).' + - '{% data variables.product.prodname_ghe_server %} 3.0 exige pelo menos uma versão dos [Utilitários de Backup do GitHub Enterprise](https://github.com/github/backup-utils) para [Backups Recuperação de Desastre](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/pt-BR/data/release-notes/3-0/0-rc2.yml b/translations/pt-BR/data/release-notes/3-0/0-rc2.yml index 0e6ed5fd3f..a770fcf802 100644 --- a/translations/pt-BR/data/release-notes/3-0/0-rc2.yml +++ b/translations/pt-BR/data/release-notes/3-0/0-rc2.yml @@ -1,25 +1,25 @@ --- date: '2021-01-29' release_candidate: true -intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +intro: As versões de candidatos devem ser testadas em ambientes que não são de produção. Para obter mais informações sobre o Programa Candidato de Versão, consulte o [Blogue do GitHub](https://github. log/2020-12-03-improving-the-ghes-release-process-release-candidates/) ou "[Sobre atualizações de novas versões](/admin/overview/about-upgrades-to-new-releases)." sections: bugs: - - heading: Fixes for known issues from Release Candidate 1 + heading: Correções para problemas conhecidos do Candidato de Versão 1 notes: - - If you disabled GitHub Actions following an unsuccessful attempt to set up GitHub Actions, then you will not be able to create the first user and use the appliance. - - The "Mandatory message viewed" audit log event was not being saved. - - '`ghe-config-apply` needed to run on a replica during an initial setup before `ghe-repl-setup` could run to start replication.' - - Removing yourself as an enterprise owner returned a 404. + - Se você desabilitou o GitHub Actions após uma tentativa mal sucedida de configurar o GitHub Actions, você não conseguirá criar o primeiro usuário e usar o dispositivo. + - O evento de log de auditoria "Mensagem obrigatória visualizada" não foi salvo. + - 'O `ghe-config-apply` necessário para ser executado em uma réplica durante uma configuração inicial antes que `ghe-repl-setup` pudesse executar para iniciar a replicação.' + - Remover você mesmo como proprietário corporativo retornou 404. - - heading: Fixes for other issues + heading: Correções para outros problemas notes: - - Issues with migrations and upgrades to 3.0.0 have been fixed. - - Backup Utilities versioning now works for release candidate versions. - - Generating a support bundle resulted in an error in the orchestrator logs. - - A large restore could result in Redis running out of memory. - - The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method. - - GitHub Actions can only be enabled if the required storage is also configured. - - '`ghe-repl-status` could silently fail if MSSQL replication is not configured.' + - Foram corrigidos os problemas com migrações e melhorias para a versão 3.0.0. + - O versionamento do Backup de Utilitários agora funciona para versões de candidato de versões. + - Gerar um pacote de suporte resultou em um erro nos registros de orquestradores. + - Uma grande restauração pode resultar no esgotamento da memória do Redis. + - A caixa de seleção para habilitar o GitHub Actions no Console de Gerenciamento agora é visível com qualquer método de autenticação. + - O GitHub Actions só pode ser habilitado se o armazenamento necessário também estiver configurado. + - 'O ''ghe-repl-status'' pode falhar silenciosamente se a replicação do MSSQL não estiver configurada.' known_issues: - - The known issues for Release Candidate 1 still apply, excluding the bug fixes listed. + - Os problemas conhecidos para o Candidato da Versão 1 ainda se aplicam, excluindo as correções de erros listadas. diff --git a/translations/pt-BR/data/reusables/actions/actions-not-verified.md b/translations/pt-BR/data/reusables/actions/actions-not-verified.md index 4c83acf907..b756fd3710 100644 --- a/translations/pt-BR/data/reusables/actions/actions-not-verified.md +++ b/translations/pt-BR/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Qualquer pessoa pode publicar uma ação em {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. +Qualquer pessoa pode publicar uma ação em {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifica algumas organizações parceiras e essas são exibidas como criadores verificados. diff --git a/translations/pt-BR/data/reusables/actions/actions-packages-set-spending-limit.md b/translations/pt-BR/data/reusables/actions/actions-packages-set-spending-limit.md index c0cb547262..9e36c87721 100644 --- a/translations/pt-BR/data/reusables/actions/actions-packages-set-spending-limit.md +++ b/translations/pt-BR/data/reusables/actions/actions-packages-set-spending-limit.md @@ -1 +1 @@ -You can set a specific spending limit or, for some accounts, allow unlimited spending. O limite de gastos aplica-se aos seus excessos conjuntos para {% data variables.product.prodname_registry %} e {% data variables.product.prodname_actions %}. +Você pode definir um limite de gastos específico ou, em algumas contas, permitir gastos ilimitados. O limite de gastos aplica-se aos seus excessos conjuntos para {% data variables.product.prodname_registry %} e {% data variables.product.prodname_actions %}. diff --git a/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md b/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md index 4babe46a83..afcae4e399 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-actions-permissions.md @@ -1,11 +1,11 @@ -1. Under "Policies", select your options. +1. Em "Políticas", selecione suas opções. - You can choose which organizations in your enterprise can use {% data variables.product.prodname_actions %}, and you can restrict access to public actions. + Você pode escolher quais organizações na empresa podem usar {% data variables.product.prodname_actions %}, e você pode restringir o acesso a ações públicas. {% if currentVersion ver_gt "enterprise-server@2.21" %} {% note %} - **Note:** To enable access to public actions, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_marketplace %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + **Observação:** Para permitir o acesso a ações públicas, você deve primeiro configurar {% data variables.product.product_location %} para conectar-se a {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações do GitHub.com usando o GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% endnote %} {% endif %} diff --git a/translations/pt-BR/data/reusables/actions/enterprise-beta.md b/translations/pt-BR/data/reusables/actions/enterprise-beta.md index 4ec540e93d..e9bfc228ba 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-beta.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,12 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**Observação:** O suporte de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} 2.22 é beta pública limitada. To review the external storage requirements and request access to the beta, 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)." +**Observação:** {% data variables.product.prodname_actions %} estava disponível para {% data variables.product.prodname_ghe_server %} 2.22 como um beta limitado. O beta terminou. {% data variables.product.prodname_actions %} está agora geralmente disponível em {% data variables.product.prodname_ghe_server %} 3.0 ou posterior. Para obter mais informações, consulte as observações sobre a versão [{% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/release-notes). + +
+ +- Para obter mais informações sobre a atualização para {% data variables.product.prodname_ghe_server %} 3.0 ou posterior, consulte "[Atualizar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)". +- Para obter mais informações sobre a configuração de {% data variables.product.prodname_actions %} após atualizar, consulte a [documentação para {% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server). {% endnote %} {% endif %} diff --git a/translations/pt-BR/data/reusables/actions/enterprise-common-prereqs.md b/translations/pt-BR/data/reusables/actions/enterprise-common-prereqs.md index 8b69ae48d3..491894d8c2 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-common-prereqs.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-common-prereqs.md @@ -1,5 +1,5 @@ -* {% data reusables.actions.enterprise-hardware-considerations %} -* TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." +* Revisar os requisitos de hardware para {% data variables.product.prodname_actions %}. 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#review-hardware-considerations)". +* O TLS deve ser configurado para o domínio de {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurar TLS](/admin/configuration/configuring-tls)". {% note %} diff --git a/translations/pt-BR/data/reusables/actions/enterprise-enable-checkbox.md b/translations/pt-BR/data/reusables/actions/enterprise-enable-checkbox.md index 0d01d079f4..3dff26053e 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-enable-checkbox.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-enable-checkbox.md @@ -1 +1 @@ -1. Select **Enable GitHub Actions**. ![Checkbox to Enable GitHub Actions](/assets/images/enterprise/management-console/enable-github-actions.png) \ No newline at end of file +1. Selecione **Habilitar o GitHub Actions**. ![Caixa de seleção para habilitar o GitHub Actions](/assets/images/enterprise/management-console/enable-github-actions.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/enterprise-hardware-considerations.md b/translations/pt-BR/data/reusables/actions/enterprise-hardware-considerations.md index 24c077bbae..a3f46bac57 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-hardware-considerations.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-hardware-considerations.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "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)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. +Se você {% if currentVersion == "enterprise-server@2.22" %} configurou o beta de{% else %} configure{% endif %} {% data variables.product.prodname_actions %} para os usuários de sua instância de {% data variables.product.prodname_ghe_server %}, recomendamos que você forneça recursos adicionais de CPU e memória. Os recursos adicionais que você precisa para provisionamento dependem do número de fluxos de trabalho que seus usuários executam simultaneamente e dos níveis gerais de atividade da sua instância. diff --git a/translations/pt-BR/data/reusables/actions/enterprise-http-proxy.md b/translations/pt-BR/data/reusables/actions/enterprise-http-proxy.md index 8bc7f63d59..80dc558807 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-http-proxy.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-http-proxy.md @@ -1 +1 @@ -If you have an **HTTP Proxy Server** configured on {% data variables.product.product_location %}, you must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." +Se você tiver um **Servidor Proxy HTTP** configurado em {% data variables.product.product_location %}, você deverá adicionar `localhost` e `127..0.1` à lista **HTTP Proxy Exclusion**. Para obter mais informações sobre como alterar as configurações de proxy, consulte "[Configurar um servidor de proxy web de saída](/admin/configuration/configuring-an-outbound-web-proxy-server)". diff --git a/translations/pt-BR/data/reusables/actions/enterprise-limit-actions-use.md b/translations/pt-BR/data/reusables/actions/enterprise-limit-actions-use.md index b3c04633ba..0fdc1017e7 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-limit-actions-use.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-limit-actions-use.md @@ -1 +1 @@ -After you enable {% data variables.product.prodname_github_connect %}, you can use policies to restrict which public actions can be used in repositories in your enterprise. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". +Após habilitar {% data variables.product.prodname_github_connect %}, você poderá usar políticas para restringir quais ações públicas podem ser usadas em repositórios na sua empresa. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". diff --git a/translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md b/translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md index fd06c5eb4c..0a90639816 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md @@ -1,3 +1,3 @@ ### Próximas etapas -After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.product.product_location %}. For your next steps, such as managing {% data variables.product.prodname_actions %} access permissions and adding self-hosted runners, return to "[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#enabling-github-actions-with-your-storage-provider)." +Depois que a execução da configuração tiver sido concluída com sucesso, {% data variables.product.prodname_actions %} será habilitado em {% data variables.product.product_location %}. Para os seus próximos passos, como gerenciar as permissões de acesso {% data variables.product.prodname_actions %} e adicionar executores auto-hospedados, retorne para "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider). diff --git a/translations/pt-BR/data/reusables/actions/enterprise-s3-permission.md b/translations/pt-BR/data/reusables/actions/enterprise-s3-permission.md index b53432227e..2c4a9a2d04 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-s3-permission.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-s3-permission.md @@ -1,4 +1,4 @@ -{% data variables.product.prodname_actions %} requires the following permissions for the access key that will access the bucket: +{% data variables.product.prodname_actions %} exige as seguintes permissões para a chave de acesso que terá acesso ao bucket: * `s3:PutObject` * `s3:GetObject` diff --git a/translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md b/translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md index 26e34ef8a4..ff74a293b1 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-s3-support-warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning:** The only supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS. Other S3 API-compatible storage providers are not supported. For more information on supported storage providers, see "[Getting started with GitHub Actions for GitHub Enterprise Server](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." +**Aviso:** Os únicos provedores de armazenamento S3 compatíveis são Amazon S3 e MinIO Gateway para NAS. Os outros provedores de armazenamento compatíveis com a API do S3 não são compatíveis. Para obter mais informações sobre provedores de armazenamento compatíveis, consulte "[Primeiros passos com GitHub Actions para o GitHub Enterprise Server](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)". {% endwarning %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/enterprise-self-signed-cert.md b/translations/pt-BR/data/reusables/actions/enterprise-self-signed-cert.md index 10c5efee2f..677953c973 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-self-signed-cert.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-self-signed-cert.md @@ -1 +1 @@ -We strongly recommend that you configure TLS on {% data variables.product.prodname_ghe_server %} with a certificate signed by a trusted authority. Although a self-signed certificate can work, extra configuration is required for your self-hosted runners, and it is not recommended for production environments. +É altamente recomendável que você configure a TLS em {% data variables.product.prodname_ghe_server %} com um certificado assinado por uma autoridade confiável. Embora um certificado autoassinado possa funcionar, é necessária uma configuração extra para os seus executores auto-hospedados, e não é recomendado para ambientes de produção. diff --git a/translations/pt-BR/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/pt-BR/data/reusables/actions/enterprise-storage-ha-backups.md index d7fd554d79..40d8538332 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-storage-ha-backups.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-storage-ha-backups.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure or AWS. +{% data variables.product.prodname_actions %} usa armazenamento externo para armazenar artefatos e registros de fluxo de trabalho. Esses dados são armazenados no seu provedor externo, como armazenamento blob do Azure, Amazon S3 ou MinIO. Como resultado, os backups de {% data variables.product.prodname_ghe_server %} e as configurações de {% data variables.product.prodname_ghe_server %} de alta disponibilidade não fornecem proteção para os dados armazenados neste armazenamento externo e, em vez disso, dependem da proteção e replicação de dados proporcionadas pelo provedor de armazenamento externo, como Azure ou AWS. diff --git a/translations/pt-BR/data/reusables/actions/environments-beta.md b/translations/pt-BR/data/reusables/actions/environments-beta.md index 5fe1386417..03ea9f6577 100644 --- a/translations/pt-BR/data/reusables/actions/environments-beta.md +++ b/translations/pt-BR/data/reusables/actions/environments-beta.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Environments, environment protection rules, and environment secrets are currently in beta and subject to change. +**Observação:** Ambientes, regras de proteção de ambiente e segredos de ambiente estão atualmente na versão beta e sujeitos a alterações. {% endnote %} diff --git a/translations/pt-BR/data/reusables/actions/visualization-beta.md b/translations/pt-BR/data/reusables/actions/visualization-beta.md index ee3ad11ef4..7b792e21b0 100644 --- a/translations/pt-BR/data/reusables/actions/visualization-beta.md +++ b/translations/pt-BR/data/reusables/actions/visualization-beta.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Note:** The workflow visualization graph for {% data variables.product.prodname_actions %} is currently in beta and subject to change. +**Observação:** O gráfico de visualização do fluxo de trabalho para {% data variables.product.prodname_actions %} está atualmente em fase beta e sujeito a alterações. {% endnote %} {% endif %} diff --git a/translations/pt-BR/data/reusables/actions/workflow-template-overview.md b/translations/pt-BR/data/reusables/actions/workflow-template-overview.md index aaf92af3de..e5e347ee59 100644 --- a/translations/pt-BR/data/reusables/actions/workflow-template-overview.md +++ b/translations/pt-BR/data/reusables/actions/workflow-template-overview.md @@ -1,3 +1,3 @@ -{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI templates that might be useful for your repository. Por exemplo, se o seu repositório contiver o código Node.js, você verá sugestões para projetos Node.js. 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. +{% data variables.product.prodname_dotcom %} fornece modelos de fluxo de trabalho pré-configurados que você pode personalizar para criar o seu próprio fluxo de trabalho de integração contínua. {% data variables.product.product_name %} analisa seu código e mostra modelos de CI que podem ser úteis para o seu repositório. Por exemplo, se o seu repositório contiver o código Node.js, você verá sugestões para projetos Node.js. 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. Você pode pesquisar a lista completa de modelos de fluxo de trabalho no repositório de {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` e no repositório {% data variables.product.product_location %}{% endif %}. diff --git a/translations/pt-BR/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/pt-BR/data/reusables/advanced-security/note-org-enable-uses-seats.md index 48f3c5a99a..2f2ac0f9db 100644 --- a/translations/pt-BR/data/reusables/advanced-security/note-org-enable-uses-seats.md +++ b/translations/pt-BR/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -1,7 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. +**Nota:** Se você habilitar {% data variables.product.prodname_GH_advanced_security %}, os committers para esses repositórios usarão estações na sua licença de {% data variables.product.prodname_GH_advanced_security %}. This option controls access to all {% data variables.product.prodname_advanced_security %} features including {% if currentVersion == "free-pro-team@latest" %}dependency review,{% endif %} {% data variables.product.prodname_code_scanning %}, and {% data variables.product.prodname_secret_scanning %}. {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/audit_log/audit-log-api-info.md b/translations/pt-BR/data/reusables/audit_log/audit-log-api-info.md index 55728a1692..c2ca223a87 100644 --- a/translations/pt-BR/data/reusables/audit_log/audit-log-api-info.md +++ b/translations/pt-BR/data/reusables/audit_log/audit-log-api-info.md @@ -1,5 +1,5 @@ -* 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 {% data variables.product.prodname_github_app %} +* O acesso às configurações da sua organização ou repositório +* As alterações nas permissões +* Os usuários adicionados ou removidos em uma organização, repositório ou equipe +* Os usuários promovidos a administradores +* Alterações nas permissões de um {% data variables.product.prodname_github_app %} diff --git a/translations/pt-BR/data/reusables/audit_log/audit-log-git-events-retention.md b/translations/pt-BR/data/reusables/audit_log/audit-log-git-events-retention.md index 3f1584bf91..506c42e702 100644 --- a/translations/pt-BR/data/reusables/audit_log/audit-log-git-events-retention.md +++ b/translations/pt-BR/data/reusables/audit_log/audit-log-git-events-retention.md @@ -1 +1 @@ -The audit log retains Git events for 7 days. This is shorter than other audit log events, which can be retained for 90 days. +O log de auditoria mantém eventos do Git por 7 dias. Isso é mais curto do que outros eventos de log de auditoria, que podem ser mantidos por 90 dias. diff --git a/translations/pt-BR/data/reusables/classroom/about-assignments.md b/translations/pt-BR/data/reusables/classroom/about-assignments.md index 65a3506229..817989b5aa 100644 --- a/translations/pt-BR/data/reusables/classroom/about-assignments.md +++ b/translations/pt-BR/data/reusables/classroom/about-assignments.md @@ -1 +1 @@ -Each assignment has a title and an optional deadline. You can choose the visibility of repositories that {% data variables.product.prodname_classroom %} creates and choose access permissions. You can also automatically grade assignments and create a dedicated space to discuss the assignment with the student. +Cada atividade tem um título e um prazo opcional. Você pode escolher a visibilidade dos repositórios que {% data variables.product.prodname_classroom %} cria e escolhe as permissões de acesso. Você também pode avaliar automaticamente as recomendações e criar um espaço dedicado para discutir a atividade com o aluno. diff --git a/translations/pt-BR/data/reusables/classroom/about-autograding.md b/translations/pt-BR/data/reusables/classroom/about-autograding.md index 04ed2b067c..b158f1d85c 100644 --- a/translations/pt-BR/data/reusables/classroom/about-autograding.md +++ b/translations/pt-BR/data/reusables/classroom/about-autograding.md @@ -1 +1 @@ -You can use autograding to automatically check a student's work for an assignment on {% data variables.product.prodname_classroom %}. You configure tests for an assignment, and the tests run immediately every time a student pushes to an assignment repository on {% data variables.product.product_location %}. The student can view the test results, make changes, and push to see new results. +Você pode usar a avaliação automática para verificar automaticamente o trabalho de um aluno para uma atividade em {% data variables.product.prodname_classroom %}. Você configura testes para uma atividade e estes são executados imediatamente toda vez que um aluno fizer envio por push para um repositório de atividade em {% data variables.product.product_location %}. O aluno pode visualizar os resultados do teste, fazer mudanças e fazer push para ver novos resultados. diff --git a/translations/pt-BR/data/reusables/classroom/about-classrooms.md b/translations/pt-BR/data/reusables/classroom/about-classrooms.md index 5d19bbb44a..fd3e82bfbe 100644 --- a/translations/pt-BR/data/reusables/classroom/about-classrooms.md +++ b/translations/pt-BR/data/reusables/classroom/about-classrooms.md @@ -1 +1 @@ -A classroom in {% data variables.product.prodname_classroom %} is where teachers and students interact during a course. Teachers can create a student roster for the classroom, then create, assign, review, and grade assignments within the classroom. +Uma sala de aula em {% data variables.product.prodname_classroom %} é onde professores e alunos interagem durante um curso. Os professores podem criar uma lista de alunos para a sala de aula e, em seguida, criar, revisar e avaliar as atividades em sala de aula. diff --git a/translations/pt-BR/data/reusables/classroom/about-online-ides.md b/translations/pt-BR/data/reusables/classroom/about-online-ides.md index 43818e691f..79c521ed58 100644 --- a/translations/pt-BR/data/reusables/classroom/about-online-ides.md +++ b/translations/pt-BR/data/reusables/classroom/about-online-ides.md @@ -1 +1 @@ -You can optionally configure an assignment to use an online integrated development environment (IDE). Online IDEs allow your students to write code, run programs, and collaborate in a browser, without installing Git and a full development toolchain on the student's computer. If you choose an online IDE for an assignment, students can still check out and run code locally on a computer with the necessary software. +Opcionalmente, você pode configurar uma atividade para usar um ambiente de desenvolvimento integrado (IDE). Os IDEs on-line permitem que seus alunos escrevam código, executem programas e colaborem em um navegador, sem instalar o Git e uma cadeia de ferramentas de desenvolvimento completa no computador do aluno. Se você escolher um IDE on-line para uma atividade, os alunos ainda poderão verificar e executar o código localmente em um computador com o o software necessário. diff --git a/translations/pt-BR/data/reusables/classroom/assignments-classroom-prerequisite.md b/translations/pt-BR/data/reusables/classroom/assignments-classroom-prerequisite.md index ccf7bc92ad..69993e3c49 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-classroom-prerequisite.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-classroom-prerequisite.md @@ -1 +1 @@ -You must create a classroom before you can create an assignment. Para obter mais informações, consulte "[Gerenciar salas de aula](/education/manage-coursework-with-github-classroom/manage-classrooms)". +Você deve criar uma sala de aula antes de poder criar uma atividade. Para obter mais informações, consulte "[Gerenciar salas de aula](/education/manage-coursework-with-github-classroom/manage-classrooms)". diff --git a/translations/pt-BR/data/reusables/classroom/assignments-click-pencil.md b/translations/pt-BR/data/reusables/classroom/assignments-click-pencil.md index 820afd5260..ef207adac0 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-click-pencil.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-click-pencil.md @@ -1 +1 @@ -1. To the right of the assignment you want to edit, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing assignment in list of assignments](/assets/images/help/classroom/assignments-click-pencil.png) +1. À direita da atividade que você deseja editar, clique em {% octicon "pencil" aria-label="The pencil icon" %}. ![Ícone de lápis para editar a atividade na lista de atividades](/assets/images/help/classroom/assignments-click-pencil.png) diff --git a/translations/pt-BR/data/reusables/classroom/assignments-group-definition.md b/translations/pt-BR/data/reusables/classroom/assignments-group-definition.md index 3143cddc70..8fdb50dcc0 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-group-definition.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-group-definition.md @@ -1 +1 @@ -A group assignment is collaborative coursework for groups of students on {% data variables.product.prodname_classroom %}. +Uma atividade em grupo é curso colaborativo para grupos de estudantes em {% data variables.product.prodname_classroom %}. diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-assign-a-deadline.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-assign-a-deadline.md index 6e8e29cc11..0cc4b646cd 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-assign-a-deadline.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-assign-a-deadline.md @@ -1,5 +1,5 @@ -Optionally, you can assign a deadline to the assignment. Under "Deadline (optional)", click in the text field, then use the date picker to assign a deadline. +Opcionalmente, você pode atribuir um prazo para a atividade. Em "Prazo (opcional)", clique no campo texto e, em seguida, use o seletor de data para atribuir um prazo.
- Date picker for assignment deadline + Seletor de data para o prazo da atividade
diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-an-online-ide.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-an-online-ide.md index 54858178a5..85ca9e9704 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-an-online-ide.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-an-online-ide.md @@ -1,5 +1,5 @@ -To choose an online IDE for the assignment, select the **Select an online IDE** drop-down menu, then click the IDE you'd like your students to use. +Para escolher um IDE on-line para a atividade, selecione o menu suspenso **Selecionar um IDE on-line** e, em seguida, clique no IDE que você deseja que seus alunos usem.
- Using the 'Select an online IDE' drop-down menu to click an online IDE for the assignment + Usar o menu suspenso "Selecionar um ID on-line" para clicar em um IDE on-line para a atividade
diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-template-repository.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-template-repository.md index 15bcb66cb5..d5a1b59572 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-template-repository.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-template-repository.md @@ -1,5 +1,5 @@ -Under "Add a template repository to give students starter code", select the **Select a repository** drop-down, then type a search query. In the list of results, click the template repository you'd like to use for starter code. +Em "Adicionar um repositório de modelo para dar o código inicial dos alunos", selecione o menu suspenso **Selecionar um repositório** e, em seguida, digite uma consulta de pesquisa. Na lista de resultados, clique no repositório modelo que você gostaria de usar para o código inicial.
- Using the 'Select a repository' drop-down menu to find a template repository to use as starter code for an assignment + Usar o menu suspenso "Selecionar um repositório" para localizar um repositório modelo e usar como código inicial para uma atividade
diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-visibility.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-visibility.md index 3f4f17e1b2..d0209122fe 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-visibility.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -1,9 +1,9 @@ -The repositories for an assignment can be public or private. If you use private repositories, only the student or team can see the feedback you provide. +Os repositórios de uma atividade podem ser públicos ou privados. Se você usar repositórios privados, apenas o aluno ou a equipe poderá ver o feedback que você fornecer. -You can also decide whether to grant students admin permissions to the repository for an assignment. Grant admin permissions if the student should be able to perform administrative tasks for the assignment repository. For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" and "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." +Você também pode decidir se deseja conceder permissões de administrador para os alunos no repositório de uma atividade. Conceda permissões de administrador se o aluno puder executar tarefas administrativas para o repositório da atividade. Para obter mais informações, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" e "[níveis de permissão do repositório para uma organização](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)". -Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**. +Em "Visibilidade do repositório", selecione uma visibilidade. Opcionalmente, selecione **Conceder acesso de administrador aos seus repositórios**.
- Visibility options for assignment repositories + Opções de visibilidade para repositórios de atividades
diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-basics.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-basics.md index b82d19fe8e..2b60557b7a 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-basics.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-basics.md @@ -1,7 +1,7 @@
-When you're done, click **Continue** to configure starter code and a development environment for the assignment. +Ao terminar, clique em **Continuar** para configurar o código inicial e um ambiente de desenvolvimento para a atividade.
- 'Continue' button + Botão "Continuar"
diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md index 4607b61065..f9ba81fd78 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md @@ -1,7 +1,7 @@
-When you're done, click **Continue** to configure automatic grading and feedback for the project. +Ao terminar, clique em **Continuar** para configurar a avaliação automática e feedback para o projeto.
- 'Continue' button + Botão "Continuar"
diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-click-create-assignment-button.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-create-assignment-button.md index 935d73f5df..88ff6d7403 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-click-create-assignment-button.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-create-assignment-button.md @@ -1,5 +1,5 @@ -To create the assignment, click **Create assignment**. +Para criar a atividade, clique em **Criar atividade**.
- 'Create assignment' button + Botão "Criar atividade"
diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-create-review-pull-request.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-create-review-pull-request.md index 5cc14ee9ff..b38587357a 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-create-review-pull-request.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-create-review-pull-request.md @@ -1,5 +1,5 @@ -To create pull requests for the discussion of feedback, select **Enable feedback pull requests**. +Para criar pull requests para a discussão de feedback, selecione **Habilitar pull requests de feedback**.
- Checkbox for 'Enable feedback pull requests' + Caixa de seleção para "Habilitar pull requests de feedback"
diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-create-the-assignment.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-create-the-assignment.md index 051e169c57..33aab51c58 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-create-the-assignment.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-create-the-assignment.md @@ -1,5 +1,5 @@ -To create an assignment, sign into {% data variables.product.prodname_classroom_with_url %} and navigate to a classroom. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click **New assignment**. +Para criar uma atividade, efetue o login em {% data variables.product.prodname_classroom_with_url %} e acesse uma sala de aula. Na aba de {% octicon "repo" aria-label="The repo icon" %} **Atividades**, clique em **Nova atividade**.
- The 'New assignment' button + Botão "Nova atividade"
diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-intro-for-environment.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-intro-for-environment.md index bda2c39723..b31cfdedf6 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-intro-for-environment.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-intro-for-environment.md @@ -1 +1 @@ -Optionally, decide whether to provide empty repositories or starter code, and preconfigure a development environment for your students. +Opcionalmente, decida se deseja fornecer repositórios vazios ou código inicial e pré-configure um ambiente de desenvolvimento para seus alunos. diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-prevent-changes.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-prevent-changes.md index 9ef39a18b9..5af277716d 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-prevent-changes.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-prevent-changes.md @@ -1,7 +1,7 @@ -You can prevent students from changing files that contain tests for autograding, or other important files in the assignment repository. +É possível impedir que os alunos alterem arquivos que contenham testes para avaliação automática ou outros arquivos importantes no repositório da atividade. -Under "Protected file paths", type relative paths within the repository to protect. +Em "Caminhos protegidos do arquivo", digite os caminhos relativos dentro do repositório a serem protegidos.
- Text field for typing protected file paths + Campo de texto para digitar caminhos de arquivos protegidos
\ No newline at end of file diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-using-autograding.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-using-autograding.md index 5f50beec64..6ea273d3bc 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-guide-using-autograding.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-using-autograding.md @@ -1,23 +1,23 @@ -{% data reusables.classroom.about-autograding %} For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." +{% data reusables.classroom.about-autograding %} Para obter mais informações, consulte "[Usar avaliação automática](/education/manage-coursework-with-github-classroom/use-autograding)". -{% data reusables.classroom.use-add-test-drop-down-to-click-grading-method %} For more information, see "[Grading methods](/education/manage-coursework-with-github-classroom/use-autograding#grading-methods)." +{% data reusables.classroom.use-add-test-drop-down-to-click-grading-method %} Para obter mais informações, consulte "[Métodos de avaliação](/education/manage-coursework-with-github-classroom/use-autograding#grading-methods)".
- Using the 'Add test' drop-down menu to click a grading method + Usar o menu suspenso "Adicionar teste" para clicar em um método de avaliação

-Define the parameters of your test case, like the name, commands, inputs, outputs, timeout, and points. When you're done, click **Save test case**. +Defina os parâmetros do seu caso de teste, como nome, comandos, entradas, saídas, tempo limite e pontos. Ao terminar, clique em **Salvar caso de teste**.
- 'Save test case' button for an autograding test + Botão "Salvar caso de teste" para um teste de avaliação automática

-You can add more tests with the **Add test** drop-down menu, and you can edit or delete existing tests with {% octicon "pencil" aria-label="The pencil icon" %} or {% octicon "trash" aria-label="The trash icon" %}. +Você pode adicionar mais testes com o menu suspenso **Adicionar teste** e também pode editar ou excluir testes existentes com {% octicon "pencil" aria-label="The pencil icon" %} ou {% octicon "trash" aria-label="The trash icon" %}.
- Pencil and trash icons to edit or delete an autograding test + Ícones de lápis e lixeira para editar ou excluir um teste de avaliação automática
\ No newline at end of file diff --git a/translations/pt-BR/data/reusables/classroom/assignments-individual-definition.md b/translations/pt-BR/data/reusables/classroom/assignments-individual-definition.md index 33425ae2c3..58ef6ddfb2 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-individual-definition.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-individual-definition.md @@ -1 +1 @@ -An individual assignment is coursework for each student who participates in a course on {% data variables.product.prodname_classroom %}. The student is intended to complete an individual assignment without help from other students. +Uma atividade individual é um curso para cada aluno que participa de um curso em {% data variables.product.prodname_classroom %}. O aluno tem a intenção de concluir uma atividade individual sem ajuda de outros alunos. diff --git a/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md index 62bd9cc2da..7cfabf65ee 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md @@ -1 +1 @@ -To prevent acceptance or submission of an assignment by students, deselect **Enable assignment invitation URL**. To edit the assignment, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit assignment**. +Para impedir a aceitação ou submissão de uma atividade por alunos, desmarque **Habilitar a URL do convite da atividade**. Para editar a atividade, clique em {% octicon "pencil" aria-label="The pencil icon" %} **Editar atividade**. diff --git a/translations/pt-BR/data/reusables/classroom/assignments-type-a-title.md b/translations/pt-BR/data/reusables/classroom/assignments-type-a-title.md index 20d32397ac..7933319415 100644 --- a/translations/pt-BR/data/reusables/classroom/assignments-type-a-title.md +++ b/translations/pt-BR/data/reusables/classroom/assignments-type-a-title.md @@ -1,5 +1,5 @@ -Type a title for the assignment. Optionally, click {% octicon "pencil" aria-label="The pencil icon" %} to edit the prefix. +Digite um título para a atividade. Opcionalmente, clique em {% octicon "pencil" aria-label="The pencil icon" %} para editar o prefixo.
- Assignment title and prefix + Título e prefixo da atividade
diff --git a/translations/pt-BR/data/reusables/classroom/classroom-creates-group-repositories.md b/translations/pt-BR/data/reusables/classroom/classroom-creates-group-repositories.md index 10cdc5924a..4b6f75104c 100644 --- a/translations/pt-BR/data/reusables/classroom/classroom-creates-group-repositories.md +++ b/translations/pt-BR/data/reusables/classroom/classroom-creates-group-repositories.md @@ -1 +1 @@ -For each group assignment, {% data variables.product.prodname_classroom %} automatically creates a single shared repository for the team to access. The repository can be empty, or you can create the repository from a template repository with starter code, documentation, tests, and other resources. The repository belongs to your organization account on {% data variables.product.product_name %}, and {% data variables.product.prodname_classroom %} grants access to teams that students create or join when accepting the assignment. +Para cada atividade em grupo, {% data variables.product.prodname_classroom %} cria automaticamente um repositório compartilhado para a equipe acessar. O repositório pode estar vazio ou você pode criar o repositório a partir de um repositório modelo com código inicial, documentação, testes e outros recursos. O repositório pertence à conta da sua organização em {% data variables.product.product_name %}, e {% data variables.product.prodname_classroom %} concede acesso a equipes que os alunos criam ou participam ao aceitar a atividade. diff --git a/translations/pt-BR/data/reusables/classroom/classroom-creates-individual-repositories.md b/translations/pt-BR/data/reusables/classroom/classroom-creates-individual-repositories.md index 4108abf9ad..a48ade628f 100644 --- a/translations/pt-BR/data/reusables/classroom/classroom-creates-individual-repositories.md +++ b/translations/pt-BR/data/reusables/classroom/classroom-creates-individual-repositories.md @@ -1 +1 @@ -When a student accepts an assignment, {% data variables.product.prodname_classroom %} automatically creates a new repository for the student. The repositories can be empty, or you can create the repositories from a template repository with starter code, documentation, tests, and other resources. Each assignment repository belongs to your organization account on {% data variables.product.product_name %}. +Quando um aluno aceita uma atividade, {% data variables.product.prodname_classroom %} cria automaticamente um novo repositório para o aluno. Os repositórios podem estar vazios ou você pode criar repositórios de um repositório modelo com código iniciante, documentação, testes e outros recursos. Cada repositório de atividade pertence à conta da sua organização em {% data variables.product.product_name %}. diff --git a/translations/pt-BR/data/reusables/classroom/classroom-enables-invitation-urls.md b/translations/pt-BR/data/reusables/classroom/classroom-enables-invitation-urls.md index 1b357c3a2d..22aba870d1 100644 --- a/translations/pt-BR/data/reusables/classroom/classroom-enables-invitation-urls.md +++ b/translations/pt-BR/data/reusables/classroom/classroom-enables-invitation-urls.md @@ -1 +1 @@ -By default, {% data variables.product.prodname_classroom %} enables an invitation URL for each assignment you create. Students can accept and submit the assignment while the invitation URL is enabled. You can share the URL with your students on your LMS, course homepage, or wherever you post assignments. Students can also navigate to the assignment on {% data variables.product.prodname_classroom %} if the student has already accepted an assignment for the classroom. +Por padrão, {% data variables.product.prodname_classroom %} habilita uma URL de convite para cada atividade que você criar. Os alunos podem aceitar e enviar a atividade enquanto a URL do convite for habilitada. Você pode compartilhar a URL com seus alunos na página inicial do curso ou onde quer que você publique as atividades. Os alunos também poderão acessar a atividade em {% data variables.product.prodname_classroom %} se o aluno já tiver aceitado uma atividade para a sala de aula. diff --git a/translations/pt-BR/data/reusables/classroom/click-assignment-in-list.md b/translations/pt-BR/data/reusables/classroom/click-assignment-in-list.md index 347d0bc108..12d61015c0 100644 --- a/translations/pt-BR/data/reusables/classroom/click-assignment-in-list.md +++ b/translations/pt-BR/data/reusables/classroom/click-assignment-in-list.md @@ -1 +1 @@ -1. In the list of assignments, click the assignment you want to view. ![Assignment in list of assignments for an classroom](/assets/images/help/classroom/click-assignment-in-list.png) +1. Na lista de atividades, clique na atividade que você deseja visualizar. ![Atividade na lista de atividades para uma sala de aula](/assets/images/help/classroom/click-assignment-in-list.png) diff --git a/translations/pt-BR/data/reusables/classroom/click-classroom-in-list.md b/translations/pt-BR/data/reusables/classroom/click-classroom-in-list.md index a6211be583..a110a577a1 100644 --- a/translations/pt-BR/data/reusables/classroom/click-classroom-in-list.md +++ b/translations/pt-BR/data/reusables/classroom/click-classroom-in-list.md @@ -1 +1 @@ -1. In the list of classrooms, click the classroom you want to view. ![Sala de aula na lista de salas de aula de uma organização](/assets/images/help/classroom/click-classroom-in-list.png) +1. Na lista de salas de aula, clique na sala de aula que você deseja visualizar. ![Sala de aula na lista de salas de aula de uma organização](/assets/images/help/classroom/click-classroom-in-list.png) diff --git a/translations/pt-BR/data/reusables/classroom/click-settings.md b/translations/pt-BR/data/reusables/classroom/click-settings.md index 9fe6b33d6b..6c59159010 100644 --- a/translations/pt-BR/data/reusables/classroom/click-settings.md +++ b/translations/pt-BR/data/reusables/classroom/click-settings.md @@ -1 +1 @@ -1. Under the classroom name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" tab for classroom](/assets/images/help/classroom/click-settings.png) +1. No nome da sala de aula, clique em {% octicon "gear" aria-label="The gear icon" %} **Configurações**. ![Aba "Configurações" da sala de aula](/assets/images/help/classroom/click-settings.png) diff --git a/translations/pt-BR/data/reusables/classroom/click-students.md b/translations/pt-BR/data/reusables/classroom/click-students.md index 13df0b1e40..590148b0c5 100644 --- a/translations/pt-BR/data/reusables/classroom/click-students.md +++ b/translations/pt-BR/data/reusables/classroom/click-students.md @@ -1 +1 @@ -1. Under the classroom name, click {% octicon "people" aria-label="The people icon" %} **Students**. !["Students" tab for classroom](/assets/images/help/classroom/click-students.png) +1. No nome da sala de aula, clique em {% octicon "people" aria-label="The people icon" %} **Alunos**. ![Aba "Alunos" da sala de aula](/assets/images/help/classroom/click-students.png) diff --git a/translations/pt-BR/data/reusables/classroom/guide-create-new-classroom.md b/translations/pt-BR/data/reusables/classroom/guide-create-new-classroom.md index d5ab6d0f93..7208b75c08 100644 --- a/translations/pt-BR/data/reusables/classroom/guide-create-new-classroom.md +++ b/translations/pt-BR/data/reusables/classroom/guide-create-new-classroom.md @@ -1,3 +1,3 @@ -1. In the list of organizations, click the organization you'd like to use for your classroom. Optionally, you can create a new organization. Para obter mais informações, consulte "[Criar uma nova organização do zero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)". ![Organization in list of organizations for creating new classroom](/assets/images/help/classroom/click-organization.png) -1. Type the name for your classroom. ![Text field for typing name of classroom](/assets/images/help/classroom/type-classroom-name.png) -1. Click **Create classroom**. ![Text field for typing name of classroom](/assets/images/help/classroom/click-create-classroom-button.png) +1. Na lista de organizações, clique na organização que você gostaria de usar para a sua sala de aula. Opcionalmente, você pode criar uma nova organização. Para obter mais informações, consulte "[Criar uma nova organização do zero](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)". ![Organização na lista de organizações para criar uma nova sala de aula](/assets/images/help/classroom/click-organization.png) +1. Digite o nome para sua sala de aula. ![Campo de texto para digitar o nome da sala de aula](/assets/images/help/classroom/type-classroom-name.png) +1. Clique em **Criar sala de aula**. ![Campo de texto para digitar o nome da sala de aula](/assets/images/help/classroom/click-create-classroom-button.png) diff --git a/translations/pt-BR/data/reusables/classroom/invitation-url-warning.md b/translations/pt-BR/data/reusables/classroom/invitation-url-warning.md index f85e808ddc..31d0c6dfdc 100644 --- a/translations/pt-BR/data/reusables/classroom/invitation-url-warning.md +++ b/translations/pt-BR/data/reusables/classroom/invitation-url-warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: Be careful where you share invitation URLs. Anyone with an invitation URL for an assignment can accept the invitation and associate a user account on {% data variables.product.product_name %} with an identifier in your roster. +**Aviso**: Tenha cuidado com o local onde você compartilha URLs de convite. Qualquer pessoa com uma URL de convite para uma atividade pode aceitar o convite e associar uma conta de usuário em {% data variables.product.product_name %} com um identificador na sua lista. {% endwarning %} diff --git a/translations/pt-BR/data/reusables/classroom/readme-contains-button-for-online-ide.md b/translations/pt-BR/data/reusables/classroom/readme-contains-button-for-online-ide.md index fac85f79f1..d277884951 100644 --- a/translations/pt-BR/data/reusables/classroom/readme-contains-button-for-online-ide.md +++ b/translations/pt-BR/data/reusables/classroom/readme-contains-button-for-online-ide.md @@ -1 +1 @@ -When a student accepts an assignment with an online 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 online IDE. +Quando um aluno aceita uma atividade com um IDE on-line, o repositório de atividade incluirá um arquivo _README.md_ com um botão especial na parte superior do arquivo. O botão vincula o aluno diretamente à área de trabalho no IDE on-line. diff --git a/translations/pt-BR/data/reusables/classroom/sign-into-github-classroom.md b/translations/pt-BR/data/reusables/classroom/sign-into-github-classroom.md index 578bf7213e..2fa8855fe2 100644 --- a/translations/pt-BR/data/reusables/classroom/sign-into-github-classroom.md +++ b/translations/pt-BR/data/reusables/classroom/sign-into-github-classroom.md @@ -1 +1 @@ -1. Sign into {% data variables.product.prodname_classroom_with_url %}. +1. Efetue o login em {% data variables.product.prodname_classroom_with_url %}. diff --git a/translations/pt-BR/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md b/translations/pt-BR/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md index 2486daf0a4..5cbe0bf6fd 100644 --- a/translations/pt-BR/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md +++ b/translations/pt-BR/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md @@ -1 +1 @@ -Under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. +Em "Adicionar testes de avaliação automática", selecione o menu suspenso **Adicionar teste** e, em seguida, clique no método de avaliação que você deseja usar. diff --git a/translations/pt-BR/data/reusables/classroom/you-can-choose-a-template-repository.md b/translations/pt-BR/data/reusables/classroom/you-can-choose-a-template-repository.md index 40eb9d273b..b5f1210867 100644 --- a/translations/pt-BR/data/reusables/classroom/you-can-choose-a-template-repository.md +++ b/translations/pt-BR/data/reusables/classroom/you-can-choose-a-template-repository.md @@ -1 +1 @@ -You can optionally choose a template repository as starter code for the assignment. The template repository must belong to your organization or be a public repository on {% data variables.product.product_name %}. +Opcionalmente, você pode escolher um repositório de modelo como código inicial para a atividade. O repositório de modelos deve pertencer à sua organização ou ser um repositório público em {% data variables.product.product_name %}. diff --git a/translations/pt-BR/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md b/translations/pt-BR/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md index e9592fb832..624c390c9e 100644 --- a/translations/pt-BR/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md +++ b/translations/pt-BR/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md @@ -1 +1 @@ -You can automatically create a pull request where you can provide feedback and answer a student's questions about an assignment. For more information about the review of changes in a pull request, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)." +Você pode criar automaticamente um pull request em que você pode fornecer feedback e responder às perguntas de um aluno sobre uma atividade. Para obter mais informações sobre a revisão das alterações em um pull request, consulte "[Revisar alterações em pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)". diff --git a/translations/pt-BR/data/reusables/code-scanning/beta.md b/translations/pt-BR/data/reusables/code-scanning/beta.md index 7d1b5dbc94..899c6c5c1e 100644 --- a/translations/pt-BR/data/reusables/code-scanning/beta.md +++ b/translations/pt-BR/data/reusables/code-scanning/beta.md @@ -2,7 +2,7 @@ {% note %} -**Note:** {% data variables.product.prodname_code_scanning_capc %} is in beta in {% data variables.product.prodname_ghe_server %} 2.22. For the generally available release of code scanning, upgrade to the latest release of {% data variables.product.prodname_ghe_server %}. +**Observação:** {% data variables.product.prodname_code_scanning_capc %} está em beta em {% data variables.product.prodname_ghe_server %} 2.22. Para a versão geralmente disponível do varredura de código, atualize para a versão mais recente de {% data variables.product.prodname_ghe_server %}. {% endnote %} diff --git a/translations/pt-BR/data/reusables/code-scanning/enabling-options.md b/translations/pt-BR/data/reusables/code-scanning/enabling-options.md index 4f0ad441cc..58e4683ba2 100644 --- a/translations/pt-BR/data/reusables/code-scanning/enabling-options.md +++ b/translations/pt-BR/data/reusables/code-scanning/enabling-options.md @@ -15,7 +15,7 @@ - Usar {% data variables.product.prodname_actions %} (consulte "Habilitar {% data variables.product.prodname_code_scanning %} usando ações") ou usar o {% data variables.product.prodname_codeql_runner %} em um sistema contínuo de integração contínua (CI) de terceiros (consulte "Varrendo o código em execução no seu sistema de CI"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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"). @@ -25,7 +25,7 @@ - Usar {% data variables.product.prodname_actions %} (consulte "Habilitar {% data variables.product.prodname_code_scanning %} usando ações") ou geradas externamente e subidas em {% data variables.product.product_name %} (consulte "Fazer upload de um arquivo SARIF em {% data variables.product.prodname_dotcom %}"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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 %}"). diff --git a/translations/pt-BR/data/reusables/code-scanning/example-configuration-files.md b/translations/pt-BR/data/reusables/code-scanning/example-configuration-files.md index 1a294850ee..a0f96fcd04 100644 --- a/translations/pt-BR/data/reusables/code-scanning/example-configuration-files.md +++ b/translations/pt-BR/data/reusables/code-scanning/example-configuration-files.md @@ -7,7 +7,7 @@ queries: - uses: security-and-quality ``` -O seguinte arquivo de configuração desabilita as consultas-padrão e especifica um conjunto de consultas personalizadas para serem executadas. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), except for the _src/node_modules_ directory, and except for files whose name ends in _.test.js_. Files in _src/node_modules_ and files with names ending _.test.js_ are therefore excluded from analysis. +O seguinte arquivo de configuração desabilita as consultas-padrão e especifica um conjunto de consultas personalizadas para serem executadas. Também configura {% data variables.product.prodname_codeql %} para fazer a varredura de arquivos no diretório _src_ (relativo à raiz), exceto o diretório _src/node_modules_ e os arquivos cujo nome termina com _.test.js_. Os arquivos em _src/node_modules_ e arquivos com nomes terminados em _.test.js_ são, portanto, excluídos da análise. ``` yaml name: "My {% data variables.product.prodname_codeql %} config" diff --git a/translations/pt-BR/data/reusables/code-scanning/not-available.md b/translations/pt-BR/data/reusables/code-scanning/not-available.md index 44df542f07..24f0aeff39 100644 --- a/translations/pt-BR/data/reusables/code-scanning/not-available.md +++ b/translations/pt-BR/data/reusables/code-scanning/not-available.md @@ -1,7 +1,7 @@ {% if currentVersion == "free-pro-team@latest" %} {% note %} -**Note:** For private and internal repositories, {% data variables.product.prodname_code_scanning %} is available when {% data variables.product.prodname_GH_advanced_security %} features are enabled for the repository. If you see the error `Advanced Security must be enabled for this repository to use code scanning`, check that {% data variables.product.prodname_GH_advanced_security %} is enabled. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". +**Observação:** Para repositórios privados e internos, {% data variables.product.prodname_code_scanning %} está disponível quando as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} são habilitadas no repositório. Se você vir o erro `dvanced Security must be enabled for this repository to use code scanning`, verifique se {% data variables.product.prodname_GH_advanced_security %} está habilitado. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". {% endnote %} {% endif %} 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 c5142332f6..ac81f29880 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,5 @@ {% note %} -**Note:** SARIF upload supports a maximum of 1000 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. +**Observação:** O upload do SARIF é compatível com um máximo de 1000 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. {% endnote %} diff --git a/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md index ba307a636c..1f64701c59 100644 --- a/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md @@ -1,3 +1,3 @@ -When running security or version updates, some ecosystems must be able to resolve all dependencies from their source to verify that updates have been successful. If your manifest or lock files contain any private dependencies, {% data variables.product.prodname_dependabot %} must be able to access the location at which those dependencies are hosted. Organization owners can grant {% data variables.product.prodname_dependabot %} access to private repositories containing dependencies for a project within the same organization. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)". +Ao executar atualizações de segurança ou versão, alguns ecossistemas devem ser capazes de resolver todas as dependências de sua fonte para verificar se as atualizações foram bem-sucedidas. Se o seu manifesto ou arquivos de bloqueio contiverem dependências privadas, {% data variables.product.prodname_dependabot %} deverá ser capaz de acessar o local em que essas dependências estão hospedadas. Os proprietários da organização podem conceder a {% data variables.product.prodname_dependabot %} acesso a repositórios privados que contêm dependências para um projeto dentro da mesma organização. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)". -Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. +Atualmente, as atualizações da versão de {% data variables.product.prodname_dependabot %} não são compatíveis com o manifesto ou arquivos de bloqueio que contenham dependências hospedadas em registros privados ou em repositórios privados {% data variables.product.prodname_dotcom %} que pertencem a uma organização diferente do projeto dependente. 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 1110f87bdb..311d184a33 100644 --- a/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md +++ b/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md @@ -1,35 +1,35 @@ -The following table shows, for each package manager: -- The YAML value to use in the *dependabot.yml* file -- The supported versions of the package manager -- Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories are supported +A tabela a seguir mostra, para cada gerenciador de pacotes: +- O valor de YAML a ser usado no arquivo *dependabot.yml* +- As versões compatíveis do gerenciador de pacotes +- Se as dependências em repositórios privados de {% data variables.product.prodname_dotcom %} são compatíveis - Whether vendored dependencies are supported -| Gerenciador de pacotes | YAML value | Supported versions | Private repositories | Vendoring | -| ---------------------- | ---------------- | ------------------------- |:--------------------:|:---------:| -| bundler | `bundler` | v1 | | **✓** | -| Cargo | `cargo` | v1 | **✓** | | -| Composer | `composer` | v1,v2 | **✓** | | -| Docker | `docker` | v1 | **✓** | | -| Elixir | `mix` | v1 | **✓** | | -| Elm | `elm` | v0.18, v0.19 | **✓** | | -| git submodule | `gitsubmodule` | N/A (no version) | **✓** | | -| GitHub Actions | `github-actions` | N/A (no version) | **✓** | | -| Go modules | `gomod` | v1 | **✓** | **✓** | -| Gradle | `gradle` | see (A) below | **✓** | | -| Maven | `maven` | see (B) below | **✓** | | -| npm | `npm` | v6 | **✓** | | -| NuGet | `nuget` | <= 4.8.
see (C) below | **✓** | | -| pip | `pip` | v20 | | | -| pipenv | `pip` | <= 2018.11.26 | | | -| pip-compile | `pip` | 5.5.0 | | | -| poetry | `pip` | v1 | | | -| Terraform | `terraform` | <= 0.11 | **✓** | | -| yarn | `npm` | v1 | | | +| Gerenciador de pacotes | Valor do YAML | Versões compatíveis | Repositórios privados | Vendoring | +| ---------------------- | ---------------- | --------------------------- |:---------------------:|:---------:| +| bundler | `bundler` | v1 | | **✓** | +| Cargo | `cargo` | v1 | **✓** | | +| Composer | `composer` | v1, v2 | **✓** | | +| Docker | `docker` | v1 | **✓** | | +| Elixir | `mix` | v1 | **✓** | | +| Elm | `elm` | v0.18, v0.19 | **✓** | | +| git submodule | `gitsubmodule` | N/A (sem versão) | **✓** | | +| GitHub Actions | `github-actions` | N/A (sem versão) | **✓** | | +| Módulos Go | `gomod` | v1 | **✓** | **✓** | +| Gradle | `gradle` | ver (A) abaixo | **✓** | | +| Maven | `maven` | ver (A) abaixo | **✓** | | +| npm | `npm` | v6, v7 | **✓** | | +| NuGet | `nuget` | <= 4.8.
veja (C) abaixo | **✓** | | +| pip | `pip` | v20 | | | +| pipenv | `pip` | <= 2018.11.26 | | | +| pip-compile | `pip` | 5.5.0 | | | +| poetry | `pip` | v1 | | | +| Terraform | `terraform` | <= 0.11 | **✓** | | +| yarn | `npm` | v1 | | | -(A) {% 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). +(A) {% data variables.product.prodname_dependabot %} não executa o Gradle, mas é compatível com atualizações dos seguintes arquivos: `build.gradle` e `build.gradle.kts` (para projetos do Kotlin). -(B) {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. +(B) {% data variables.product.prodname_dependabot %} não usa o Maven, mas é compatível com atualizações para arquivos `pom.xml`. -(C) {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8. +(C) {% data variables.product.prodname_dependabot %} não executa o NuGet CLI, mas é compatível com a maioria das funcionalidades até a versão 4.8. -For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. Por exemplo, se você usa o `poetry` para gerenciar suas dependências do Python e quer que {% data variables.product.prodname_dependabot %} monitore seu arquivo de manifesto de dependência para novas versões, use `pacote-ecosystem: "pip"` no seu arquivo *dependabot.yml*. +Para gerentes de pacote como `pipenv` e `poetry`, você precisa usar o valor `do pip` do YAML. Por exemplo, se você usa o `poetry` para gerenciar suas dependências do Python e quer que {% data variables.product.prodname_dependabot %} monitore seu arquivo de manifesto de dependência para novas versões, use `pacote-ecosystem: "pip"` no seu arquivo *dependabot.yml*. diff --git a/translations/pt-BR/data/reusables/desktop/choose-clone-repository.md b/translations/pt-BR/data/reusables/desktop/choose-clone-repository.md index f3041322b5..38b874772f 100644 --- a/translations/pt-BR/data/reusables/desktop/choose-clone-repository.md +++ b/translations/pt-BR/data/reusables/desktop/choose-clone-repository.md @@ -1 +1,13 @@ 1. No menu **File** (Arquivo), clique em **Clone Repository** (Clonar repositório). + + {% mac %} + + ![Opção de menu Clone (Clonar) no app Mac](/assets/images/help/desktop/clone-file-menu-mac.png) + + {% endmac %} + + {% windows %} + + ![Opção de menu Clone (Clonar) no app Windows](/assets/images/help/desktop/clone-file-menu-windows.png) + + {% endwindows %} diff --git a/translations/pt-BR/data/reusables/desktop/choose-local-path.md b/translations/pt-BR/data/reusables/desktop/choose-local-path.md new file mode 100644 index 0000000000..10c5e8fb0a --- /dev/null +++ b/translations/pt-BR/data/reusables/desktop/choose-local-path.md @@ -0,0 +1,13 @@ +1. Click **Choose...** and navigate to a local path where you want to clone the repository. + + {% mac %} + + ![Botão Choose (Escolher)](/assets/images/help/desktop/clone-choose-button-mac.png) + + {% endmac %} + + {% windows %} + + ![Botão Choose (Escolher)](/assets/images/help/desktop/clone-choose-button-win.png) + + {% endwindows %} diff --git a/translations/pt-BR/data/reusables/desktop/click-clone.md b/translations/pt-BR/data/reusables/desktop/click-clone.md new file mode 100644 index 0000000000..1c31a9c722 --- /dev/null +++ b/translations/pt-BR/data/reusables/desktop/click-clone.md @@ -0,0 +1,14 @@ +1. Clique em **Clone** (Clonar). + + {% mac %} + + ![Botão Clone (Clonar)](/assets/images/help/desktop/clone-button-mac.png) + + {% endmac %} + + {% windows %} + + ![Botão Clone (Clonar)](/assets/images/help/desktop/clone-button-win.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/desktop/cloning-location-tab.md b/translations/pt-BR/data/reusables/desktop/cloning-location-tab.md index e7e8e05431..48d1cf39be 100644 --- a/translations/pt-BR/data/reusables/desktop/cloning-location-tab.md +++ b/translations/pt-BR/data/reusables/desktop/cloning-location-tab.md @@ -1 +1,13 @@ 1. Clique na aba que corresponde à localização do repositório que você deseja clonar. Você também pode clicar **URL** para inserir manualmente o local do repositório. + + {% mac %} + + ![Guias Location (Local) no menu Clone a repository (Clonar um repositório)](/assets/images/help/desktop/choose-repository-location-mac.png) + + {% endmac %} + + {% windows %} + + ![Guias Location (Local) no menu Clone a repository (Clonar um repositório)](/assets/images/help/desktop/choose-repository-location-win.png) + + {% endwindows %} diff --git a/translations/pt-BR/data/reusables/desktop/cloning-repository-list.md b/translations/pt-BR/data/reusables/desktop/cloning-repository-list.md index 9ed4fcc3e5..23ae18755c 100644 --- a/translations/pt-BR/data/reusables/desktop/cloning-repository-list.md +++ b/translations/pt-BR/data/reusables/desktop/cloning-repository-list.md @@ -1 +1,14 @@ 1. Escolha o repositório que você quer clonar na lista. + + + {% mac %} + + ![Clonar uma lista de repositórios](/assets/images/help/desktop/clone-a-repository-list-mac.png) + + {% endmac %} + + {% windows %} + + ![Clonar uma lista de repositórios](/assets/images/help/desktop/clone-a-repository-list-win.png) + + {% endwindows %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/desktop/delete-tag.md b/translations/pt-BR/data/reusables/desktop/delete-tag.md index 40d455b880..4e3e9430fc 100644 --- a/translations/pt-BR/data/reusables/desktop/delete-tag.md +++ b/translations/pt-BR/data/reusables/desktop/delete-tag.md @@ -1,4 +1,4 @@ -1. Right-click the commit. +1. Clique com o botão direito no commit. - - If a commit has only one tag, click **Delete Tag TAG NAME**. ![Select the delete tag menu item](/assets/images/help/desktop/select-delete-tag.png) - - If a commit has multiple tags, hover over **Delete Tag...** and then click the tag that you want to delete. ![Hover over the delete tag menu](/assets/images/help/desktop/delete-tag-multiple.png) \ No newline at end of file + - Se um commit tiver apenas uma tag, clique em **Excluir NOME DA TAG**. ![Selecione o item de menu de exclusão da tag](/assets/images/help/desktop/select-delete-tag.png) + - Se um commit tiver várias tags, passe o mouse sobre **Excluir Tag...** e, em seguida, clique na tag que você deseja excluir. ![Passe sobre o menu de exclusão de tag](/assets/images/help/desktop/delete-tag-multiple.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/desktop/fork-type-prompt.md b/translations/pt-BR/data/reusables/desktop/fork-type-prompt.md new file mode 100644 index 0000000000..1067dab748 --- /dev/null +++ b/translations/pt-BR/data/reusables/desktop/fork-type-prompt.md @@ -0,0 +1,42 @@ +1. If you plan to use this fork for contributing to the original upstream repository, click **To contribute to the parent project**. + + {% mac %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/mac-fork-options-prompt.png) + + {% endmac %} + + {% windows %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/windows-fork-options-prompt.png) + + {% endwindows %} + +2. If you plan to use this fork for a project not connected to the upstream, click **For my own purposes**. + + {% mac %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/mac-fork-own-purposes.png) + + {% endmac %} + + {% windows %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/windows-fork-own-purposes.png) + + {% endwindows %} + +3. Click **Continue**. + + {% mac %} + + ![The continue button](/assets/images/help/desktop/mac-forking-continue.png) + + {% endmac %} + + {% windows %} + + ![The continue button](/assets/images/help/desktop/windows-forking-continue.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/desktop/open-repository-settings.md b/translations/pt-BR/data/reusables/desktop/open-repository-settings.md new file mode 100644 index 0000000000..5e298edc85 --- /dev/null +++ b/translations/pt-BR/data/reusables/desktop/open-repository-settings.md @@ -0,0 +1,14 @@ +1. Open the **Repository** menu, then click **Repository settings...**. + + {% mac %} + + ![Repository settings menu option in the Mac app](/assets/images/help/desktop/mac-repository-settings.png) + + {% endmac %} + + {% windows %} + + ![Repository settings menu option in the Windows app](/assets/images/help/desktop/windows-repository-settings.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/desktop/select-fork-behavior.md b/translations/pt-BR/data/reusables/desktop/select-fork-behavior.md new file mode 100644 index 0000000000..d23e827e4b --- /dev/null +++ b/translations/pt-BR/data/reusables/desktop/select-fork-behavior.md @@ -0,0 +1,28 @@ +1. Click **Fork behavior**, then select how you want to use the fork. + + {% mac %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-menu-contribute.png) + + {% endmac %} + + {% windows %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-menu-contribute.png) + + {% endwindows %} + +2. Clique em **Salvar**. + + {% mac %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-save.png) + + {% endmac %} + + {% windows %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-save.png) + + {% endwindows %} + \ 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 02b360dafd..46e856d6dd 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 @@ -10,4 +10,4 @@ Quando você cria uma pull request a partir de um repositório bifurcado para o Fluxos de trabalho não são executados em repositórios bifurcados por padrão. Você deve habilitar o GitHub Actions na aba **Actions** (Ações) do repositório bifurcado. -{% data reusables.actions.forked-secrets %} The permissions for the `GITHUB_TOKEN` in forked repositories is read-only. Para obter mais informações, consulte "[Autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". +{% data reusables.actions.forked-secrets %} As permissões para o `GITHUB_TOKEN` em repositórios bifurcados são somente leitura. Para obter mais informações, consulte "[Autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". diff --git a/translations/pt-BR/data/reusables/discussions/about-categories-and-formats.md b/translations/pt-BR/data/reusables/discussions/about-categories-and-formats.md index a17ca2ca53..22c7349ca6 100644 --- a/translations/pt-BR/data/reusables/discussions/about-categories-and-formats.md +++ b/translations/pt-BR/data/reusables/discussions/about-categories-and-formats.md @@ -1 +1 @@ -All discussions must be created in a category, and repository administrators and maintainers define the categories for a repository. Categories can contain open-ended conversations, or conversations with a question/answer format. +Todas as discussões devem ser criadas em uma categoria e os administradores e mantenedores de repositório definem as categorias de um repositório. As categorias podem conter conversas abertas ou conversas com formato de pergunta/resposta. diff --git a/translations/pt-BR/data/reusables/discussions/about-discussions.md b/translations/pt-BR/data/reusables/discussions/about-discussions.md index c61b8b0f0a..721b760b06 100644 --- a/translations/pt-BR/data/reusables/discussions/about-discussions.md +++ b/translations/pt-BR/data/reusables/discussions/about-discussions.md @@ -1 +1 @@ -Discussions are an open forum for conversation among maintainers and the community for a project on {% data variables.product.product_name %}. +As discussões são feitas um fórum aberto para a conversa entre os mantenedores e a comunidade para um projeto em {% data variables.product.product_name %}. diff --git a/translations/pt-BR/data/reusables/discussions/click-discussion-in-list.md b/translations/pt-BR/data/reusables/discussions/click-discussion-in-list.md index 2a96e33ffd..bf45665571 100644 --- a/translations/pt-BR/data/reusables/discussions/click-discussion-in-list.md +++ b/translations/pt-BR/data/reusables/discussions/click-discussion-in-list.md @@ -1 +1 @@ -1. Na lista de discussões, clique na discussão que você deseja visualizar. ![Discussion in list of discussions for a repository](/assets/images/help/discussions/click-discussion-in-list.png) +1. Na lista de discussões, clique na discussão que você deseja visualizar. ![Discussão na lista de discussões de um repositório](/assets/images/help/discussions/click-discussion-in-list.png) diff --git a/translations/pt-BR/data/reusables/discussions/discussions-tab.md b/translations/pt-BR/data/reusables/discussions/discussions-tab.md index 67795aa5ae..2774e346f9 100644 --- a/translations/pt-BR/data/reusables/discussions/discussions-tab.md +++ b/translations/pt-BR/data/reusables/discussions/discussions-tab.md @@ -1 +1 @@ -1. Under your repository name, click {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions**. !["Discussions" tab for a repository](/assets/images/help/discussions/repository-discussions-tab.png) +1. No nome do seu repositório, clique em {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussões**. ![Aba "Discussões" de um repositório](/assets/images/help/discussions/repository-discussions-tab.png) diff --git a/translations/pt-BR/data/reusables/discussions/edit-categories.md b/translations/pt-BR/data/reusables/discussions/edit-categories.md index 6f4f6af574..98f655b4f9 100644 --- a/translations/pt-BR/data/reusables/discussions/edit-categories.md +++ b/translations/pt-BR/data/reusables/discussions/edit-categories.md @@ -1 +1 @@ -1. To the right of "Categories", click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing categories](/assets/images/help/discussions/click-edit-categories.png) +1. À direita das "Categorias", clique em {% octicon "pencil" aria-label="The pencil icon" %}. ![Ícone de lápis para edição de categorias](/assets/images/help/discussions/click-edit-categories.png) diff --git a/translations/pt-BR/data/reusables/discussions/edit-category-details.md b/translations/pt-BR/data/reusables/discussions/edit-category-details.md index 07bcebadd8..f88ed27651 100644 --- a/translations/pt-BR/data/reusables/discussions/edit-category-details.md +++ b/translations/pt-BR/data/reusables/discussions/edit-category-details.md @@ -1 +1 @@ -Edite o emoji, título, descrição e formato de discussão para a categoria. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." +Edite o emoji, título, descrição e formato de discussão para a categoria. Para obter mais informações sobre formatos de discussão, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". diff --git a/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md b/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md index 88327eecec..781c88e5a7 100644 --- a/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md +++ b/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md @@ -1,5 +1,5 @@ -You can enable or disable discussions for a repository. +Você pode habilitar ou desabilitar discussões para um repositório. {% 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 do repositório](/assets/images/help/discussions/public-repo-settings.png) -1. Under "Features", select **Discussions**. ![Checkbox under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/select-discussions-checkbox.png) +1. Em "Funcionalidades", selecione **discussões**. ![Caixa de seleção em "Funcionalidades" para habilitar ou desabilitar discussões para um repositório](/assets/images/help/discussions/select-discussions-checkbox.png) diff --git a/translations/pt-BR/data/reusables/discussions/github-recognizes-members.md b/translations/pt-BR/data/reusables/discussions/github-recognizes-members.md index b6874b910d..04c40dd7b5 100644 --- a/translations/pt-BR/data/reusables/discussions/github-recognizes-members.md +++ b/translations/pt-BR/data/reusables/discussions/github-recognizes-members.md @@ -1 +1 @@ -{% data variables.product.prodname_dotcom %} will automatically recognize community members who contribute the most comments marked as answers to discussions with a question/answer format. +{% data variables.product.prodname_dotcom %} reconhecerá automaticamente os integrantes da comunidade que contribuem com a maioria dos comentários marcados como respostas para discussões com um formato de pergunta/resposta. diff --git a/translations/pt-BR/data/reusables/discussions/marking-a-comment-as-an-answer.md b/translations/pt-BR/data/reusables/discussions/marking-a-comment-as-an-answer.md index 80305caedf..62f9e832f0 100644 --- a/translations/pt-BR/data/reusables/discussions/marking-a-comment-as-an-answer.md +++ b/translations/pt-BR/data/reusables/discussions/marking-a-comment-as-an-answer.md @@ -1,14 +1,14 @@ -You can mark a comment in the discussion as an answer to the discussion if a discussion is within a category that accepts answers. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)". +Você pode marcar um comentário na discussão como uma resposta para a discussão se uma discussão estiver dentro de uma categoria que aceita respostas. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)". -When you mark a question as an answer, {% data variables.product.product_name %} will highlight the comment and replies to the comment to help visitors quickly find the answer. +Ao marcar uma pergunta como resposta, {% data variables.product.product_name %} destacará o comentário e as respostas ao comentário para ajudar os visitantes a encontrar a resposta rapidamente. -![Comment marked as answer to a discussion](/assets/images/help/discussions/comment-marked-as-answer.png) +![Comentário marcado como resposta para uma discussão](/assets/images/help/discussions/comment-marked-as-answer.png) -You can't mark a threaded comment in response to a comment as the answer to a discussion. You also can't mark a minimized comment as the answer to a discussion. +You can't mark a threaded comment in response to a comment as the answer to a discussion. Você também não pode marcar um comentário minimizado como resposta para uma discussão. {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} -1. In the list of discussions, click the unanswered discussion you want to mark as answered. ![Unanswered discussion](/assets/images/help/discussions/unanswered-discussion.png) -1. In the discussion, find the comment you want to mark as the answer. -1. In the upper-right corner of the comment, click {% octicon "check-circle" aria-label="The circular check icon" %}. !["Mark as answer" circular check icon for marking comment as answer in a discussion](/assets/images/help/discussions/comment-mark-as-answer-button.png) -1. Optionally, to unmark a comment as the answer, click {% octicon "check-circle-fill" aria-label="The filled circular check icon" %}. +1. Na lista de discussões, clique na discussão não respondida que você deseja marcar como respondida. ![Discussão não respondida](/assets/images/help/discussions/unanswered-discussion.png) +1. Na discussão, encontre o comentário que deseja marcar como resposta. +1. No canto superior direito do comentário, clique em {% octicon "check-circle" aria-label="The circular check icon" %}. ![Ícone circular de verificação "Marcar como resposta" para marcar comentário como resposta em uma discussão](/assets/images/help/discussions/comment-mark-as-answer-button.png) +1. Opcionalmente, para desmarcar um comentário como a resposta, clique em {% octicon "check-circle-fill" aria-label="The filled circular check icon" %}. diff --git a/translations/pt-BR/data/reusables/discussions/repository-category-limit.md b/translations/pt-BR/data/reusables/discussions/repository-category-limit.md index 293d3632b5..ca61bf579f 100644 --- a/translations/pt-BR/data/reusables/discussions/repository-category-limit.md +++ b/translations/pt-BR/data/reusables/discussions/repository-category-limit.md @@ -1 +1 @@ -Each repository can have up to 10 categories. +Cada repositório pode ter até 10 categorias. diff --git a/translations/pt-BR/data/reusables/discussions/starting-a-discussion.md b/translations/pt-BR/data/reusables/discussions/starting-a-discussion.md index 242e3abf9b..88b94072ac 100644 --- a/translations/pt-BR/data/reusables/discussions/starting-a-discussion.md +++ b/translations/pt-BR/data/reusables/discussions/starting-a-discussion.md @@ -1,6 +1,6 @@ {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} -1. Click **New discussion**. !["New discussion" button within the "Discussions" tab for a repository](/assets/images/help/discussions/new-discussion-button.png) -1. Select the **Select Category** drop-down menu, and click a category for your discussion. !["Select Category" drop-down menu and list of available categories in a repository](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png) -1. Type a title and body for your discussion. ![Text fields for new discussion's title and body](/assets/images/help/discussions/new-discussion-title-and-body-fields.png) -1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) +1. Clique em **Nova discussão**. ![Botão "Nova discussão" dentro da aba "Discussões" para um repositório](/assets/images/help/discussions/new-discussion-button.png) +1. Menu suspenso **Selecionar categoria** e clique em uma categoria para a sua discussão. ![Menu suspenso "Selecionar categoria" e lista de categorias disponíveis em repositório](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png) +1. Digite um título e texto para sua discussão. ![Campos de texto para o título e texto da nova discussão](/assets/images/help/discussions/new-discussion-title-and-body-fields.png) +1. Clique em **Iniciar discussão**. ![Botão "Iniciar discussão"](/assets/images/help/discussions/new-discussion-start-discussion-button.png) diff --git a/translations/pt-BR/data/reusables/discussions/you-can-categorize-discussions.md b/translations/pt-BR/data/reusables/discussions/you-can-categorize-discussions.md index bb05316d77..4b8aed210e 100644 --- a/translations/pt-BR/data/reusables/discussions/you-can-categorize-discussions.md +++ b/translations/pt-BR/data/reusables/discussions/you-can-categorize-discussions.md @@ -1 +1 @@ -You can categorize discussions to help community members begin conversations in the right place, and to help community members find related discussions. +Você pode categorizar as discussões para ajudar os integrantes da comunidade a iniciar as conversas no lugar certo e para ajudar os integrantes da comunidade a encontrar as discussões relacionadas. diff --git a/translations/pt-BR/data/reusables/discussions/you-can-convert-an-issue.md b/translations/pt-BR/data/reusables/discussions/you-can-convert-an-issue.md index 1421256e1f..eeaabf9c09 100644 --- a/translations/pt-BR/data/reusables/discussions/you-can-convert-an-issue.md +++ b/translations/pt-BR/data/reusables/discussions/you-can-convert-an-issue.md @@ -1 +1 @@ -If an issue turns out to be a question or open-ended conversation instead of a work item to track and prioritize, you can convert the issue to a discussion. +Se um problema for uma pergunta ou conversa aberta em vez de um item de trabalho para rastrear e priorizar, você poderá converter o problema em uma discussão. diff --git a/translations/pt-BR/data/reusables/discussions/you-can-use-discussions.md b/translations/pt-BR/data/reusables/discussions/you-can-use-discussions.md index 27c1ba7cb2..35751c7260 100644 --- a/translations/pt-BR/data/reusables/discussions/you-can-use-discussions.md +++ b/translations/pt-BR/data/reusables/discussions/you-can-use-discussions.md @@ -1 +1 @@ -You can use discussions to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." \ No newline at end of file +Você pode usar discussões para perguntar e responder a perguntas, compartilhar informações, fazer anúncios e conduzir ou participar de conversas sobre um projeto. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/discussions/you-cannot-convert-a-discussion.md b/translations/pt-BR/data/reusables/discussions/you-cannot-convert-a-discussion.md index 9e9b687b67..437eb2c818 100644 --- a/translations/pt-BR/data/reusables/discussions/you-cannot-convert-a-discussion.md +++ b/translations/pt-BR/data/reusables/discussions/you-cannot-convert-a-discussion.md @@ -1 +1 @@ -You cannot convert a discussion to an issue. \ No newline at end of file +Você não pode converter uma discussão em um problema. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/education/click-get-teacher-benefits.md b/translations/pt-BR/data/reusables/education/click-get-teacher-benefits.md index 25bbacd747..ae9762e6e3 100644 --- a/translations/pt-BR/data/reusables/education/click-get-teacher-benefits.md +++ b/translations/pt-BR/data/reusables/education/click-get-teacher-benefits.md @@ -1 +1 @@ -1. Under "Individuals", click **Get teacher benefits**. !["Get teacher benefits" on {% data variables.product.prodname_education %} homepage](/assets/images/help/education/click-get-teacher-benefits.png) +1. Em "Indivíduos", clique em **Obter benefícios para professores**. !["Obter benefícios para professores" na página inicial de {% data variables.product.prodname_education %}](/assets/images/help/education/click-get-teacher-benefits.png) diff --git a/translations/pt-BR/data/reusables/education/educator-requirements.md b/translations/pt-BR/data/reusables/education/educator-requirements.md index 5738b11a67..ad77c52d42 100644 --- a/translations/pt-BR/data/reusables/education/educator-requirements.md +++ b/translations/pt-BR/data/reusables/education/educator-requirements.md @@ -1,6 +1,6 @@ -To apply for an educator or researcher discount, you must meet the following requirements. +Para solicitar desconto de um educador ou pesquisador, você deve atender aos seguintes requisitos. - Ser um educador, integrante do corpo docente ou pesquisador. - Tenha um endereço de e-mail verificável emitido pela escola. - Faça upload dos documentos que comprovam a sua afiliação à escola. -- Have a user account on {% data variables.product.product_name %}. +- Ter uma conta de usuário em {% data variables.product.product_name %}. diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md b/translations/pt-BR/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md new file mode 100644 index 0000000000..2e1246eb1d --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md @@ -0,0 +1 @@ +Se você comprou {% data variables.product.prodname_enterprise %} por meio de um Contrato da Microsoft Enterprise, você pode conectar seu ID de assinatura Azure à sua conta corporativa para habilitar e pagar pelo uso de {% data variables.product.prodname_actions %} e de {% data variables.product.prodname_registry %}, além dos valores incluindo na sua conta. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/payment-information-tab.md b/translations/pt-BR/data/reusables/enterprise-accounts/payment-information-tab.md new file mode 100644 index 0000000000..b692aa0d0b --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/payment-information-tab.md @@ -0,0 +1 @@ +1. Em "Cobrança", clique em **Informações de pagamento**. diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md index afcce00090..31a426ecfb 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/user-provisioning-release-stage.md @@ -1,5 +1,5 @@ {% note %} -**Note:** User provisioning for organizations in your enterprise accounts, currently supported only for Okta, is in private beta and subject to change. Para solicitar acesso ao beta, [contact our account management team](https://enterprise.github.com/contact) (entre em contato com nossa equipe de gerenciamento de conta). +**Nota:** O provisionamento de usuários para organizações em contas corporativas, atualmente compatível apenas com Okta, está em versão beta privada e está sujeito a alterações. Para solicitar acesso ao beta, [contact our account management team](https://enterprise.github.com/contact) (entre em contato com nossa equipe de gerenciamento de conta). {% endnote %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/verified-domains-tab.md b/translations/pt-BR/data/reusables/enterprise-accounts/verified-domains-tab.md index 35420a6888..9613a09be2 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/verified-domains-tab.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/verified-domains-tab.md @@ -1 +1 @@ -1. Under "Settings", click **Verified domains**. !["Verified domains" tab](/assets/images/help/enterprises/verified-domains-tab.png) \ No newline at end of file +1. Em "Configurações", clique em **Domínios verificados**. ![Aba "Domínios verificados"](/assets/images/help/enterprises/verified-domains-tab.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/verifying-domains-release-phase.md b/translations/pt-BR/data/reusables/enterprise-accounts/verifying-domains-release-phase.md index 331fb63c15..a0777fd66e 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/verifying-domains-release-phase.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/verifying-domains-release-phase.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Verifying an enterprise account's domain is currently in beta and subject to change. +**Observação:** A verificação do domínio da conta corporativa está atualmente na versão beta e sujeita a alterações. {% endnote %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise_installation/about-adjusting-resources.md b/translations/pt-BR/data/reusables/enterprise_installation/about-adjusting-resources.md new file mode 100644 index 0000000000..2fb1c4e950 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise_installation/about-adjusting-resources.md @@ -0,0 +1 @@ +Para obter mais informações sobre o ajuste de recursos para uma instância existente, consulte "[aumentar a capacidade de armazenamento](/enterprise/admin/installation/increasing-storage-capacity)" e "[aumentar recursos de CPU ou memória](/enterprise/admin/installation/increasing-cpu-or-memory-resources)". diff --git a/translations/pt-BR/data/reusables/enterprise_installation/aws-supported-instance-types.md b/translations/pt-BR/data/reusables/enterprise_installation/aws-supported-instance-types.md index 4029c84072..c4111d57d8 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/aws-supported-instance-types.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/aws-supported-instance-types.md @@ -1,37 +1,13 @@ -{% data variables.product.prodname_ghe_server %} é suportado nos seguintes tipos de instância do EC2. Para obter mais informações, consulte [the AWS EC2 instance type overview page](http://aws.amazon.com/ec2/instance-types/). +{% data variables.product.prodname_ghe_server %} é compatível nos seguintes tamanhos de instância do EC2. Para obter mais informações, consulte [the AWS EC2 instance type overview page](http://aws.amazon.com/ec2/instance-types/). -| Tipo de instância EC2 | Modelo | -| --------------------- | ---------------------------------- | -| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | - -| Tipo de instância EC2 | Modelo | -| --------------------- | ---------------------------------- | -| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | - -| Tipo de instância EC2 | Modelo | -| --------------------- | -------------------------------------------------------------------- | -| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | - -| Tipo de instância EC2 | Modelo | -| --------------------- | --------------------- | -| M3 | m3.xlarge, m3.2xlarge | - -| Tipo de instância EC2 | Modelo | -| --------------------- | ----------------------------------------------------------- | -| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | - -| Tipo de instância EC2 | Modelo | -| --------------------- | --------------------------------------------------------------------- | -| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | - -| Tipo de instância EC2 | Modelo | -| --------------------- | -------------------------------------------------------------------- | -| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | - -| Tipo de instância EC2 | Modelo | -| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} - -| Tipo de instância EC2 | Modelo | -| --------------------- | ------------------------ | -| X1 | x1.16xlarge, x1.32xlarge | +| Tipo | Tamanho | +|:---- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | +| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | +| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | +| M3 | m3.xlarge, m3.2xlarge | +| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | +| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | +| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | +| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} +| X1 | x1.16xlarge, x1.32xlarge | diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 29c948b6c8..4b7d59a85c 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,6 +1,5 @@ -- [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} -- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} -- [Optional features](#optional-features){% endif %} +- [Requisitos mínimos](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} +- [Funcionalidades de beta em {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %} - [Armazenamento](#storage) - [CPU e memória](#cpu-and-memory) @@ -8,20 +7,7 @@ Recomendamos diferentes configurações de hardware, dependendo do número de licenças de usuário para {% data variables.product.product_location %}. Se você fornecer mais recursos do que os requisitos mínimos, sua instância terá um desempenho e uma escala melhores. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - -- Você deve configurar pelo menos um executor para fluxos de trabalho de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)." -- Você deve configurar o armazenamento externo do blob. 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)". -- You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations. - - | Máximo de trabalhos por minuto | Additional vCPUs | Additional memory | - |:------------------------------ | ----------------:| -----------------:| - | Testes rápidos | 4 | 30.5 GB | - | 25 | 8 | 61 GB | - | 35 | 16 | 122 GB | - | 100 | 32 | 244 GB | - -{% endif %} +{% data reusables.enterprise_installation.hardware-rec-table %} #### Armazenamento @@ -31,7 +17,7 @@ A sua instância exige um disco de dados persistente separado do disco raiz. Par {% if currentVersion ver_gt "enterprise-server@2.21" %} -If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. 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)". +Para configurar{% if currentVersion == "enterprise-server@2.22" %} beta de{% endif %} {% data variables.product.prodname_actions %}, você deve fornecer armazenamento externo de blob. 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)". {% endif %} @@ -39,7 +25,7 @@ Você pode redimensionar o disco raiz da sua instância criando uma nova instân #### CPU e memória -O {% data variables.product.prodname_ghe_server %} exige mais recursos de CPU e memória, dependendo dos níveis de atividade para usuários, automações e integrações. +Os recursos de CPU e memória que {% data variables.product.prodname_ghe_server %} exige dependem dos níveis de atividade para usuários, automações e integrações. {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data reusables.actions.enterprise-hardware-considerations %}{% endif %} {% data reusables.enterprise_installation.increasing-cpus-req %} diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md index 461702e2fd..c4c1ccb005 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,20 +1,20 @@ -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." +**Nota**: Se você se juntou ao beta para {% data variables.product.prodname_actions %} ou {% data variables.product.prodname_registry %} e habilitou as funcionalidades, a sua instância irá exigir recursos adicionais de hardware. Os requisitos mínimos para uma instância com recursos beta habilitados estão em **negrito** na tabela a seguir. Para obter mais informações, consulte "[Recursos Beta em {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)". {% endnote %} {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -| Licenças de usuário | vCPUs | Memória | Armazenamento anexado | Armazenamento raiz | -|:---------------------------------------- | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| ------------------:| -| Teste, demonstração ou 10 usuários leves | 2
ou [**4**](#optional-features) | 16 GB
ou [**32 GB**](#optional-features) | 100 GB
ou [**150 GB**](#optional-features) | 200 GB | -| 10-3000 | 4
ou [**8**](#optional-features) | 32 GB
ou [**48 GB**](#optional-features) | 250 GB
ou [**300 GB**](#optional-features) | 200 GB | -| 3000-5000 | 8
ou [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | -| 5000-8000 | 12
ou [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | -| 8000-10000+ | 16
ou [**20**](#optional-features) | 128 GB
ou [**160 GB**](#optional-features) | 1000 GB | 200 GB | +| Licenças de usuário | vCPUs | Memória | Armazenamento anexado | Armazenamento raiz | +|:---------------------------------------- | -----:| -------:| ---------------------:| ------------------:| +| Teste, demonstração ou 10 usuários leves | 4 | 32 GB | 150 GB | 200 GB | +| 10-3000 | 8 | 48 GB | 300 GB | 200 GB | +| 3000-5000 | 12 | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 16 | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 20 | 160 GB | 1000 GB | 200 GB | {% else %} @@ -28,22 +28,20 @@ {% endif %} -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)." +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +Se você planeja configurar {% data variables.product.prodname_actions %} para a sua instância, você deverá fornecer recursos adicionais. Você também deve configurar pelo menos um executor auto-hospedado para executar fluxos de trabalho. 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)". + +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} #### Recursos do beta em {% data variables.product.prodname_ghe_server %} 2.22 -You can sign up for beta features available in {% data variables.product.prodname_ghe_server %} 2.22 such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [release notes for the 2.22 series](https://enterprise.github.com/releases/series/2.22#release-2.22.0) on the {% data variables.product.prodname_enterprise %} website. +{% data variables.product.prodname_ghe_server %} 2.22 ofereceu funcionalidades em beta, como {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} e {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte as observações sobre a versão [{% data variables.product.prodname_ghe_server %} 2.22](/enterprise-server@2.22/admin/release-notes#2.22.0). -If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". - -{% elsif currentVersion ver_gt "enterprise-server@2.22" %} - -#### Optional features - -You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. 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)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." - -If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +Se você habilitou funcionalidades em beta para {% data variables.product.prodname_ghe_server %} 2.22, sua instância irá exigir recursos adicionais de hardware. Para obter mais informações, consulte "[Requisitos mínimos](#minimum-requirements)". {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise_installation/image-urls-viewable-warning.md b/translations/pt-BR/data/reusables/enterprise_installation/image-urls-viewable-warning.md index 2a26ad6d64..d576258836 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/image-urls-viewable-warning.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/image-urls-viewable-warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning:** If you add an image attachment to a pull request or issue comment, anyone can view the anonymized image URL without authentication{% if enterpriseServerVersions contains currentVersion %}, even if the pull request is in a private repository, or if private mode is enabled. To prevent unauthorized access to the images, ensure that you restrict network access to the systems that serve the images, including {% data variables.product.product_location %}{% endif %}.{% if currentVersion == "github-ae@latest" %} To prevent unauthorized access to image URLs on {% data variables.product.product_name %}, consider restricting network traffic to your enterprise. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)."{% endif %} +**Aviso:** Se você adicionar um anexo de imagem a um pull request ou comentário de problema, qualquer pessoa poderá ver a URL de imagem anônima sem autenticação{% if enterpriseServerVersions contains currentVersion %}, mesmo se o pull request estiver em um repositório privado, ou se o modo privado estiver habilitado. Para evitar o acesso não autorizado às imagens, limite o acesso à rede para os sistemas que servem as imagens, incluindo {% data variables.product.product_location %}{% endif %}.{% if currentVersion == "github-ae@latest" %} Para impedir acesso não autorizado às URLs de imagens em {% data variables.product.product_name %}, considere restringir o tráfego de rede para a sua empresa. Para obter mais informações, consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)".{% endif %} {% endwarning %} diff --git a/translations/pt-BR/data/reusables/enterprise_management_console/actions.md b/translations/pt-BR/data/reusables/enterprise_management_console/actions.md index 4c789eca69..a21c3893a7 100644 --- a/translations/pt-BR/data/reusables/enterprise_management_console/actions.md +++ b/translations/pt-BR/data/reusables/enterprise_management_console/actions.md @@ -1 +1 @@ -1. Na barra lateral esquerda, clique em **Actions** (Ações). ![Actions tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-actions.png) +1. Na barra lateral esquerda, clique em **Actions** (Ações). ![Aba Ações na barra lateral de configurações](/assets/images/enterprise/management-console/sidebar-actions.png) diff --git a/translations/pt-BR/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/pt-BR/data/reusables/enterprise_management_console/advanced-security-license.md index 29c2a88163..ceb87149df 100644 --- a/translations/pt-BR/data/reusables/enterprise_management_console/advanced-security-license.md +++ b/translations/pt-BR/data/reusables/enterprise_management_console/advanced-security-license.md @@ -1 +1 @@ -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 %} and {% data variables.product.prodname_secret_scanning %}. A licença do {% data variables.product.prodname_advanced_security %} dá a você e aos seus usuários acesso a recursos que ajudam a tornar seus repositórios e códigos mais seguros. {% if currentVersion ver_gt "enterprise-server@2.22" %}For more information, see "[About GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" or contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} +Se você não pode ver **{% data variables.product.prodname_advanced_security %}** na barra lateral. Isso significa que sua licença não inclui suporte para funcionalidades de {% data variables.product.prodname_advanced_security %}, incluindo {% data variables.product.prodname_code_scanning %} e {% data variables.product.prodname_secret_scanning %}. A licença do {% data variables.product.prodname_advanced_security %} dá a você e aos seus usuários acesso a recursos que ajudam a tornar seus repositórios e códigos mais seguros. {% if currentVersion ver_gt "enterprise-server@2.22" %}Para obter mais informações, consulte "[Sobre o GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" ou entre em contato com {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/pt-BR/data/reusables/enterprise_migrations/ready-to-import-migrations.md index 0cdbb1f880..28da3b362c 100644 --- a/translations/pt-BR/data/reusables/enterprise_migrations/ready-to-import-migrations.md +++ b/translations/pt-BR/data/reusables/enterprise_migrations/ready-to-import-migrations.md @@ -1 +1 @@ -1. To prepare the archived migration data for import into a {% data variables.product.prodname_ghe_server %} instance, see "[Preparing to migrate data to your enterprise](/enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise)". +1. Para preparar os dados de migração arquivados para fazer a importação para uma instância de {% data variables.product.prodname_ghe_server %}, consulte "[Preparar-se para migrar dados para a sua empresa](/enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise)". diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/message-preview-save.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/message-preview-save.md index c834bf66b4..b84bc18f9d 100644 --- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/message-preview-save.md +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/message-preview-save.md @@ -1,2 +1,2 @@ -1. Optionally, to preview your message, click **Preview**. ![Preview message button](/assets/images/enterprise/site-admin-settings/message-preview-button.png) +1. Opcionalmente, para pré-visualizar a sua mensagem, clique em **Visualizar**. ![Botão Visualizar mensagem](/assets/images/enterprise/site-admin-settings/message-preview-button.png) 1. Clique em **Save changes** (Salvar alterações). ![Botão Edit message (Editar mensagem)](/assets/images/enterprise/site-admin-settings/message-save-changes-button.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/gated-features/auto-merge.md b/translations/pt-BR/data/reusables/gated-features/auto-merge.md index 72a58ba07d..acfb4dddff 100644 --- a/translations/pt-BR/data/reusables/gated-features/auto-merge.md +++ b/translations/pt-BR/data/reusables/gated-features/auto-merge.md @@ -1 +1 @@ -Auto-merge for pull requests 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" %}{% data reusables.gated-features.more-info %}{% endif %} \ No newline at end of file +Auto-merge for pull requests 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 %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/code-scanning.md b/translations/pt-BR/data/reusables/gated-features/code-scanning.md index 69e6abf27f..35598cce54 100644 --- a/translations/pt-BR/data/reusables/gated-features/code-scanning.md +++ b/translations/pt-BR/data/reusables/gated-features/code-scanning.md @@ -1 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled. +{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository. +{%- else %} +{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/pt-BR/data/reusables/gated-features/discussions.md b/translations/pt-BR/data/reusables/gated-features/discussions.md index 5ada0a25ee..864301ba41 100644 --- a/translations/pt-BR/data/reusables/gated-features/discussions.md +++ b/translations/pt-BR/data/reusables/gated-features/discussions.md @@ -1 +1 @@ -{% data variables.product.prodname_discussions %} is available in beta for public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} +{% data variables.product.prodname_discussions %} está disponível em beta para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/pt-BR/data/reusables/gated-features/environments.md b/translations/pt-BR/data/reusables/gated-features/environments.md index 916fe9c1d3..1e1d9104d0 100644 --- a/translations/pt-BR/data/reusables/gated-features/environments.md +++ b/translations/pt-BR/data/reusables/gated-features/environments.md @@ -1 +1 @@ -{% data reusables.gated-features.actions-shared %} Environments, environment protection rules, and environment secrets are available in public repositories for all products and in private repositories for {% data variables.product.prodname_enterprise %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% data reusables.gated-features.actions-shared %} Os ambientes, regras de proteção de ambiente e segredos de ambiente estão disponíveis em repositórios públicos para todos os produtos e em repositórios privados para {% data variables.product.prodname_enterprise %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/pages.md b/translations/pt-BR/data/reusables/gated-features/pages.md index 31caf392d2..0e25d3c673 100644 --- a/translations/pt-BR/data/reusables/gated-features/pages.md +++ b/translations/pt-BR/data/reusables/gated-features/pages.md @@ -1 +1 @@ -{% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_pages %} is available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}. {% endif %}{% data variables.product.prodname_pages %} 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 %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% if currentVersion == "github-ae@latest" %}{% data variables.product.prodname_pages %} está disponível em repositórios internos e privados com {% data variables.product.prodname_ghe_managed %}. {% endif %}{% data variables.product.prodname_pages %} está disponível em repositórios públicos com {% data variables.product.prodname_free_user %} e {% data variables.product.prodname_free_team %} para organizações, e em repositórios públicos e privados com {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/private-pages.md b/translations/pt-BR/data/reusables/gated-features/private-pages.md index 3fb7f0a3a7..9fa0fe959a 100644 --- a/translations/pt-BR/data/reusables/gated-features/private-pages.md +++ b/translations/pt-BR/data/reusables/gated-features/private-pages.md @@ -1 +1 @@ -Access control for {% data variables.product.prodname_pages %} sites is available in private repositories with {% data variables.product.prodname_ghe_cloud %}. +O controle de acesso para sites de {% data variables.product.prodname_pages %} está disponível em repositórios privados com {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/pt-BR/data/reusables/gated-features/protected-branches.md b/translations/pt-BR/data/reusables/gated-features/protected-branches.md index ffae769bab..7eec25324e 100644 --- a/translations/pt-BR/data/reusables/gated-features/protected-branches.md +++ b/translations/pt-BR/data/reusables/gated-features/protected-branches.md @@ -1 +1 @@ -{% if currentVersion == "github-ae@latest" %}Protected branches are available in internal and private repositories with {% data variables.product.prodname_ghe_managed %}, {% else%}Protected branches are available {% endif %}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 %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} +{% if currentVersion == "github-ae@latest" %}Os branches protegidos estão disponíveis em repositórios internos e privados com {% data variables.product.prodname_ghe_managed %}, {% else%}Os branches protegidos estão disponíveis {% endif %}em repositórios públicos com {% data variables.product.prodname_free_user %} e {% data variables.product.prodname_free_team %} para organizações, e em repositórios públicos e privados com {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md index 535fa5cd9d..338d25f7b8 100644 --- a/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md +++ b/translations/pt-BR/data/reusables/gist/cannot-convert-public-gists-to-secret.md @@ -1 +1 @@ -After creating a gist, you cannot convert it from {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} to secret. +Após criar um gist, você não poderá convertê-lo de {% if currentVersion == "github-ae@latest" %}interno{% else %}público{% endif %} para secreto. diff --git a/translations/pt-BR/data/reusables/github-actions/actions-billing.md b/translations/pt-BR/data/reusables/github-actions/actions-billing.md index 04d5d9ded7..6a6f7b296e 100644 --- a/translations/pt-BR/data/reusables/github-actions/actions-billing.md +++ b/translations/pt-BR/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} usage is free for both public repositories and self-hosted runners. Para repositórios privados, cada conta {% data variables.product.prodname_dotcom %} recebe uma certa quantidade de minutos e armazenamento gratuitos, dependendo do produto usado com a conta. Any usage beyond the included amounts is controlled by spending limits. +O uso de {% data variables.product.prodname_actions %} é grátis tanto para repositórios públicos quanto para executores auto-hospedados. Para repositórios privados, cada conta {% data variables.product.prodname_dotcom %} recebe uma certa quantidade de minutos e armazenamento gratuitos, dependendo do produto usado com a conta. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-brief.md index 20d912fb21..70eec6819c 100644 --- a/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-brief.md +++ b/translations/pt-BR/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, which prevents additional usage of minutes or storage for private repositories beyond the amounts included with your account. If you pay your account by invoice, your account will have an unlimited default spending limit. +Se você é um cliente que realiza cobrança mensal, a sua conta terá um limite de gastos padrão de $ 0, o que impede o uso adicional de minutos ou armazenamento para repositórios privados além dos valores incluídos na sua conta. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-detailed.md index 0ce0975905..2bd7e655dc 100644 --- a/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-detailed.md +++ b/translations/pt-BR/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, 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 %} charges usage to the account that owns the repository where a workflow is run. Quaisquer cupons em sua conta não se aplicam a {% data variables.product.prodname_actions %} excessos. +If you have an unlimited spending limit or a spending limit set higher than $0, 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 o uso da conta do repositório em que um fluxo de trabalho é executado. Quaisquer cupons em sua conta não se aplicam a {% data variables.product.prodname_actions %} excessos. diff --git a/translations/pt-BR/data/reusables/github-actions/contacting-support.md b/translations/pt-BR/data/reusables/github-actions/contacting-support.md index bb90d99862..a5aeaa9637 100644 --- a/translations/pt-BR/data/reusables/github-actions/contacting-support.md +++ b/translations/pt-BR/data/reusables/github-actions/contacting-support.md @@ -1,4 +1,4 @@ -If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} category](https://github.community/c/code-to-cloud/github-actions/41). +Se precisar de ajuda com algo relacionado com a configuração do fluxo de trabalho, como sintaxe, executores hospedados em {% data variables.product.prodname_dotcom %}, ou ações de criação, procure por um tópico existente ou comece um novo na categoria de [{% data variables.product.prodname_gcf %} {% data variables.product.prodname_actions %} ](https://github.community/c/code-to-cloud/github-actions/41). Se você tiver comentários ou solicitações de recursos para {% data variables.product.prodname_actions %}, compartilhe-os na {% data variables.contact.contact_feedback_actions %}. 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 eb59a94fbb..bae721470a 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 @@ -1,8 +1,8 @@ -| Ambiente virtual | Etiqueta de fluxo de trabalho YAML | -| -------------------- | ---------------------------------- | -| Windows Server 2019 | `windows-latest` ou `windows-2019` | -| Ubuntu 20.04 | `ubuntu-20.04` | -| Ubuntu 18.04 | `ubuntu-latest` ou `ubuntu-18.04` | -| Ubuntu 16.04 | `ubuntu-16.04` | -| macOS Big Sur 11.0 | `macos-11.0` | -| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | +| Ambiente virtual | Etiqueta de fluxo de trabalho YAML | +| -------------------- | -------------------------------------------- | +| Windows Server 2019 | `windows-latest` ou `windows-2019` | +| Ubuntu 20.04 | `ubuntu-latest` (see note) or `ubuntu-20.04` | +| Ubuntu 18.04 | `ubuntu-latest` (see note) or `ubuntu-18.04` | +| Ubuntu 16.04 | `ubuntu-16.04` | +| macOS Big Sur 11.0 | `macos-11.0` | +| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | diff --git a/translations/pt-BR/data/reusables/github-actions/ubuntu-runner-preview.md b/translations/pt-BR/data/reusables/github-actions/ubuntu-runner-preview.md index f07ebd2ff4..6eb91edc13 100644 --- a/translations/pt-BR/data/reusables/github-actions/ubuntu-runner-preview.md +++ b/translations/pt-BR/data/reusables/github-actions/ubuntu-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Nota:** O ambiente virtual do Ubuntu 20.04 é atualmente fornecido apenas como visualização. A etiqueta de fluxo de trabalho YAML `ubuntu-latest` ainda usa o ambiente virtual Ubuntu 18.04. +**Note:** The `ubuntu-latest` label is currently being migrated from the Ubuntu 18.04 virtual environment to Ubuntu 20.04. Specifying the `ubuntu-latest` label during the migration might use either virtual environment. To explicitly use Ubuntu 20.04 or Ubuntu 18.04, specify `ubuntu-20.04` or `ubuntu-18.04`. When the migration is complete, `ubuntu-latest` will use the Ubuntu 20.04 virtual environment. For more information about the migration, see "[Ubuntu-latest workflows will use Ubuntu-20.04](https://github.com/actions/virtual-environments/issues/1816)." {% endnote %} diff --git a/translations/pt-BR/data/reusables/organizations/organizations_include.md b/translations/pt-BR/data/reusables/organizations/organizations_include.md index a43d34345a..a3bb2ba3c2 100644 --- a/translations/pt-BR/data/reusables/organizations/organizations_include.md +++ b/translations/pt-BR/data/reusables/organizations/organizations_include.md @@ -6,3 +6,4 @@ As organizações incluem: - [Equipes aninhadas que refletem a estrutura da sua empresa ou grupo](/articles/about-teams) com permissões de acesso em cascata e menções {% if currentVersion != "github-ae@latest" %} - A capacidade para os proprietários da organização verem a autenticação de dois fatores [two-factor authentication (2FA) status](/articles/about-two-factor-authentication) (status de autenticação de dois fatores) - A opção de [Exigir que todos os integrantes da organização usem a autenticação de dois fatores](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} +{% if currentVersion == "free-pro-team@latest" %}- The option to purchase a license for {% data variables.product.prodname_GH_advanced_security %} and use the features on private repositories. {% data reusables.advanced-security.more-info-ghas %}{% endif %} diff --git a/translations/pt-BR/data/reusables/pages/new-or-existing-repo.md b/translations/pt-BR/data/reusables/pages/new-or-existing-repo.md index 8cdab25f1c..4087ad034b 100644 --- a/translations/pt-BR/data/reusables/pages/new-or-existing-repo.md +++ b/translations/pt-BR/data/reusables/pages/new-or-existing-repo.md @@ -1,3 +1,5 @@ Se o seu site for um projeto independente, você pode criar um novo repositório para armazenar o código-fonte do seu site. Se o seu site estiver associado a um projeto existente, você pode adicionar o código-fonte {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" or currentVersion == "github-ae@latest" %}a esse repositório do projeto, em uma pasta de `/docs` no branch padrão ou em um branch diferente.{% else %}para o seu site para um branch de `páginas gh-pages` ou uma pasta de `docs` no branch `mestre` no repositório do projeto.{% endif %} Por exemplo, se você estiver criando um site para publicar a documentação de um projeto que já está em {% data variables.product.product_name %}, você deverá armazenar o código-fonte para o site no mesmo repositório do projeto. +{% if currentVersion == "free-pro-team@latest" %}If the account that owns the repository uses {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_free_team %}, the repository must be public.{% endif %} + Se você deseja criar um site em um repositório existente, pule para a seção "[Criar o seu site](#creating-your-site). diff --git a/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md b/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md index 04d4ddeb1c..a6af500463 100644 --- a/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md +++ b/translations/pt-BR/data/reusables/pages/private_pages_are_public_warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet{% if currentVersion == "free-pro-team@latest" %} by default{% endif %}, even if the repository for the site is private or internal.{% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Otherwise, if{% else %} If{% endif %} you have sensitive data in your site's repository, you may want to remove the data before publishing. For more information, see{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" and "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site)."{% else %}."{% endif %} +**Aviso**: {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}Se o administrador do site tiver ativado páginas públicas, {% endif %}{% data variables.product.prodname_pages %} sites estão disponíveis publicamente na internet{% if currentVersion == "free-pro-team@latest" %} por padrão{% endif %}, Mesmo que o repositório para o site seja privado ou interno. {% if currentVersion == "free-pro-team@latest" %} {% data reusables.pages.about-private-publishing %} Caso contrário, se{% else %} Se{% endif %} tiver dados confidenciais no repositório do seu site, poderá remover os dados antes de publicar. Para mais informações, consulte{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}[Configurando {% data variables.product.prodname_pages %} para a sua empresa](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages)" e{% endif %} "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility){% if currentVersion == "free-pro-team@latest" %}" e "[Alterando a visibilidade do seu site {% data variables.product.prodname_pages %}](/github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site).{% else %}."{% endif %} {% endwarning %} diff --git a/translations/pt-BR/data/reusables/pull_requests/you-can-auto-merge.md b/translations/pt-BR/data/reusables/pull_requests/you-can-auto-merge.md index 784c6733e9..1fdcea56d1 100644 --- a/translations/pt-BR/data/reusables/pull_requests/you-can-auto-merge.md +++ b/translations/pt-BR/data/reusables/pull_requests/you-can-auto-merge.md @@ -1,3 +1,3 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} You can configure a pull request to merge automatically when all merge requirements are met. Para obter mais informações, consulte "[Fazer merge automático de um pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)". -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md index f458924c12..43c93c2f5f 100644 --- a/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| Tecla | Tipo | Descrição | -| ------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. Se a ação é `closed` e a chave `merged` é `false`, o pull request foi fechado com commits não mesclados. Se a ação for `closed` e a chave `merged` for `verdadeira`, o pull request foi mesclado. | +| Tecla | Tipo | Descrição | +| ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação que foi executada. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. Se a ação é `closed` e a chave `merged` é `false`, o pull request foi fechado com commits não mesclados. Se a ação for `closed` e a chave `merged` for `verdadeira`, o pull request foi mesclado. | diff --git a/translations/pt-BR/data/variables/action_code_examples.yml b/translations/pt-BR/data/variables/action_code_examples.yml index 8f9aecb699..c9b792d4b1 100644 --- a/translations/pt-BR/data/variables/action_code_examples.yml +++ b/translations/pt-BR/data/variables/action_code_examples.yml @@ -24,20 +24,20 @@ - etiquetas - title: Add releases to GitHub - description: Publish Github releases in an action + description: Publish GitHub releases in an action languages: 'Dockerfile, Shell' href: elgohr/Github-Release-Action tags: - releases - - publishing + - publicar - title: Publish a docker image to Dockerhub - description: A Github Action used to build and publish Docker images + description: A GitHub Action used to build and publish Docker images languages: 'Dockerfile, Shell' href: elgohr/Publish-Docker-Github-Action tags: - docker - - publishing + - publicar - build - title: Create an issue using content from a file @@ -53,7 +53,7 @@ href: softprops/action-gh-release tags: - releases - - publishing + - publicar - title: GitHub Project Automation+ description: Automate GitHub Project cards with any webhook event @@ -104,7 +104,7 @@ languages: 'JavaScript, Shell' href: ad-m/github-push-action tags: - - publishing + - publicar - title: Generate release notes based on your events description: Action to auto generate a release note based on your events @@ -112,7 +112,7 @@ href: Decathlon/release-notes-generator-action tags: - releases - - publishing + - publicar - title: Create a GitHub wiki page based on the provided markdown file description: Create a GitHub wiki page based on the provided markdown file @@ -120,10 +120,10 @@ href: Decathlon/wiki-page-creator-action tags: - wiki - - publishing + - publicar - title: Label your Pull Requests auto-magically (using committed files) - description: Github action to label your pull requests auto-magically (using committed files) + description: GitHub action to label your pull requests auto-magically (using committed files) languages: 'TypeScript, Dockerfile, JavaScript' href: Decathlon/pull-request-labeler-action tags: @@ -132,7 +132,7 @@ - etiquetas - title: Add Label to your Pull Requests based on the author team name - description: Github action to label your pull requests based on the author name + description: GitHub action to label your pull requests based on the author name languages: 'TypeScript, JavaScript' href: JulienKode/team-labeler-action tags: @@ -332,4 +332,4 @@ languages: 'TypeScript, JavaScript' href: peaceiris/actions-gh-pages tags: - - publishing + - publicar diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml index 9f88ea0a03..4d7a6959dd 100644 --- a/translations/pt-BR/data/variables/product.yml +++ b/translations/pt-BR/data/variables/product.yml @@ -147,10 +147,10 @@ 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://docs.github.com/rest{% elsif enterpriseServerVersions contains currentVersion %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif currentVersion == "github-ae@latest" %}https://docs.github.com/github-ae@latest/rest{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% endif %} #Use this inside command-line code blocks #Enterprise OAuth paths that don't include "/graphql" or "/api/v3" oauth_host_code: >- @@ -159,10 +159,10 @@ device_authorization_url: >- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}[`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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/graphql{% endif %} 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 5b5debce04..251556fb90 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 @@ -7,7 +7,7 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -type: 'обзор' +type: overview --- {% data reusables.actions.enterprise-beta %} @@ -63,7 +63,7 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe {% data reusables.github-actions.usage-api-requests %} - **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %} -### Supported operating systems for self-hosted runners +### Supported architectures and operating systems for self-hosted runners The following operating systems are supported for the self-hosted runner application. @@ -92,6 +92,14 @@ The following operating systems are supported for the self-hosted runner applica - macOS 10.13 (High Sierra) or later +#### Architectures + +The following processor architectures are supported for the self-hosted runner application. + +- `x64` - Linux, macOS, Windows. +- `ARM64` - Linux only. +- `ARM32` - Linux only. + {% if enterpriseServerVersions contains currentVersion %} ### Supported actions on self-hosted runners 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 77537c94ae..49ccca3a22 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 @@ -29,7 +29,7 @@ A self-hosted runner automatically receives certain labels when it is added to { * `self-hosted`: Default label applied to all self-hosted runners. * `linux`, `windows`, or `macOS`: Applied depending on operating system. -* `x86`, `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. +* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. You can use your workflow's YAML to send jobs to a combination of these labels. In this example, a self-hosted runner that matches all three labels will be eligible to run the job: diff --git a/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md index f81a2a8d43..ee1a447cb5 100644 --- a/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md @@ -41,12 +41,17 @@ Windows virtual machines are configured to run as administrators with User Accou ### Supported runners and hardware resources -Each virtual machine has the same hardware resources available. +Hardware specification for Windows and Linux virtual machines: - 2-core CPU - 7 GB of RAM memory - 14 GB of SSD disk space +Hardware specification for macOS virtual machines: +- 3-core CPU +- 14 GB of RAM memory +- 14 GB of SSD disk space + {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} @@ -71,9 +76,13 @@ The software tools included in {% data variables.product.prodname_dotcom %}-host {% data variables.product.prodname_dotcom %}-hosted runners include the operating system's default built-in tools, in addition to the packages listed in the above references. For example, Ubuntu and macOS runners include `grep`, `find`, and `which`, among other default tools. -Workflow logs include a link to the preinstalled tools on the runner. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." +Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will tell you the the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -If there is a tool that you'd like to request, please open an issue at [actions/virtual-environments](https://github.com/actions/virtual-environments). +We recommend using actions to interact with the software installed on runners. This approach has several benefits: +- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters +- It ensures the tool versions used in your workflow will remain the same regardless of software updates + +If there is a tool that you'd like to request, please open an issue at [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners. ### IP addresses diff --git a/translations/ru-RU/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/ru-RU/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index 08a27ed2a3..185e01118d 100644 --- a/translations/ru-RU/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/ru-RU/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -73,7 +73,7 @@ If the server on which you are running {% endif %} #### Enabling code scanning for individual repositories -After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. 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)." +After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." ### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %} If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. diff --git a/translations/ru-RU/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/ru-RU/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index bb3988d67d..bbfc6b83c1 100644 --- a/translations/ru-RU/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md +++ b/translations/ru-RU/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md @@ -20,7 +20,7 @@ For encryption in transit, {% data variables.product.product_name %} uses Transp The key that you provide is stored in a hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages. -To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and delete your encryption key. Note that deleting your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation. +To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation. ### Adding or updating an encryption key @@ -48,24 +48,24 @@ Your 2048 bit RSA private key should be in PEM format, for example in a file cal curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` -### Deleting your encryption key +### Disabling your encryption key -To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by deleting your encryption key. +To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled. -To unfreeze your enterprise after you've deleted your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)." - -1. To delete your key and disable encryption at rest, use the `DELETE /enterprise/encryption` endpoint. +1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently. ```shell curl -X DELETE http(s)://hostname/api/v3/enterprise/encryption ``` -2. Optionally, check the status of the delete operation. +2. Optionally, check the status of the delete operation. It takes approximately ten minutes to disable encryption at rest. ```shell curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` +To unfreeze your enterprise after you've disabled your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)." + ### Дополнительная литература - "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation diff --git a/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md index 1a14b5b568..856905c01e 100644 --- a/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/ru-RU/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -29,6 +29,26 @@ versions: {% endnote %} +{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %} + +### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later + +Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table. + +| User licenses | vCPUs | Memory | Attached storage | Root storage | +|:------------------------------ | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:| +| Trial, demo, or 10 light users | **4**
_Up from 2_ | **32 GB**
_Up from 16 GB_ | **150 GB**
_Up from 100 GB_ | 200 GB | +| 10 to 3,000 | **8**
_Up from 4_ | **48 GB**
_Up from 32 GB_ | **300 GB**
_Up from 250 GB_ | 200 GB | +| 3,000 to 5000 | **12**
_Up from 8_ | 64 GB | 500 GB | 200 GB | +| 5,000 to 8000 | **16**
_Up from 12_ | 96 GB | 750 GB | 200 GB | +| 8,000 to 10,000+ | **20**
_Up from 16_ | **160 GB**
_Up from 128 GB_ | 1000 GB | 200 GB | + +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% endif %} + ### Taking a snapshot A snapshot is a checkpoint of a virtual machine (VM) at a point in time. We highly recommend taking a snapshot before upgrading your virtual machine so that if an upgrade fails, you can revert your VM back to the snapshot. If you're upgrading to a new feature release, you must take a VM snapshot. If you're upgrading to a patch release, you can attach the existing data disk. diff --git a/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md index 93e0cf66c1..6707aa8640 100644 --- a/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/ru-RU/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -9,13 +9,7 @@ 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-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} @@ -23,11 +17,33 @@ versions: This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies. +{% endif %} + ### Review hardware considerations +{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %} + +{% note %} + +**Note**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." + +{% endnote %} + +{% endif %} + {% data reusables.actions.enterprise-hardware-considerations %} -{% endif %} +For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform. + +- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) +- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) +- [Облачная платформа Google](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) +- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) +- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) +- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations) +- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations) + +{% data reusables.enterprise_installation.about-adjusting-resources %} ### External storage requirements @@ -55,7 +71,7 @@ To enable {% data variables.product.prodname_actions %} on {% data variables.pro ### Enabling {% data variables.product.prodname_actions %} -{% 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/). +{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." ### Дополнительная литература diff --git a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md index 60a7dc7a2e..62473efca8 100644 --- a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md +++ b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md @@ -8,40 +8,40 @@ versions: free-pro-team: '*' --- -### Cloning repositories -Repositories on {% data variables.product.prodname_dotcom %} exist as remote repositories. You can clone public repositories owned by other people. You can clone your own repository to create a local copy on your computer and sync between the two locations. +### About local repositories +Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer. + +You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. For more information, see "[Syncing your branch](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)." + +When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. For more information, see "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)." + +When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)". You can also clone a repository directly from {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)". -{% mac %} +### Cloning a repository {% data reusables.desktop.choose-clone-repository %} - ![Clone menu option in the Mac app](/assets/images/help/desktop/clone-file-menu-mac.png) {% data reusables.desktop.cloning-location-tab %} - ![Location tabs in the Clone a repository menu](/assets/images/help/desktop/choose-repository-location-mac.png) {% data reusables.desktop.cloning-repository-list %} - ![Clone a repository list](/assets/images/help/desktop/clone-a-repository-list-mac.png) -4. Click **Choose...** and, using the Finder window, navigate to a local path where you want to clone the repository. ![The choose button](/assets/images/help/desktop/clone-choose-button-mac.png) -5. Click **Clone**. ![The clone button](/assets/images/help/desktop/clone-button-mac.png) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} -{% endmac %} - -{% windows %} +### Forking a repository +If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork. {% data reusables.desktop.choose-clone-repository %} - ![Clone menu option in the Windows app](/assets/images/help/desktop/clone-file-menu-windows.png) {% data reusables.desktop.cloning-location-tab %} - ![Location tabs in the Clone a repository menu](/assets/images/help/desktop/choose-repository-location-win.png) {% data reusables.desktop.cloning-repository-list %} - ![Clone a repository list](/assets/images/help/desktop/clone-a-repository-list-win.png) -4. Click **Choose...** and, using Windows Explorer, navigate to a local path where you want to clone the repository. ![The choose button](/assets/images/help/desktop/clone-choose-button-win.png) -5. Click **Clone**. ![The clone button](/assets/images/help/desktop/clone-button-win.png) +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} +{% data reusables.desktop.fork-type-prompt %} -{% endwindows %} +### Managing fork behavior +You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}. -### Forking repositories -To contribute to a project where you don't have write access, you can use {% data variables.product.prodname_desktop %} to create a fork of the repository. Changes on your fork don't affect the original repository. You can commit changes on your fork, then open a pull request to the original repository with your proposed changes. For more information, see "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)." +{% data reusables.desktop.open-repository-settings %} +{% data reusables.desktop.select-fork-behavior %} -1. If you've cloned a repository where you don't have write access and try to commit changes, {% data variables.product.prodname_desktop %} will warn that "You don't have write access to **REPOSITORY**. Click **create a fork**. ![Create a fork link](/assets/images/help/desktop/create-a-fork.png) -3. Click **Fork this repository**. ![Fork this repo button](/assets/images/help/desktop/fork-this-repo-button.png) -4. To view your fork on {% data variables.product.prodname_dotcom %}, in the top right corner of {% data variables.product.prodname_dotcom %}, click your profile picture, then click **Your repositories**. ![Your repositories link](/assets/images/help/profile/your-repositories.png) +### Дополнительная литература +- [About remote repositories](/github/using-git/about-remote-repositories) diff --git a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 6e8a51401d..36bfcc0b4c 100644 --- a/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/ru-RU/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -9,7 +9,7 @@ versions: ### About tags in {% data variables.product.prodname_desktop %} -{% data variables.product.prodname_desktop %} allows you to create annotated tags. You can use a tag to mark an individual point in your repository's history, including a version number for a release. For more information about release tags, see "[About releases](/github/administering-a-repository/about-releases)." +{% data variables.product.prodname_desktop %} allows you to create annotated tags. Tags are associated with commits, so you can use a tag to mark an individual point in your repository's history, including a version number for a release. For more information about release tags, see "[About releases](/github/administering-a-repository/about-releases)." {% data reusables.desktop.tags-push-with-commits %} @@ -44,3 +44,7 @@ versions: {% data reusables.desktop.history-tab %} {% data reusables.desktop.delete-tag %} + +### Дополнительная литература + +- "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation diff --git a/translations/ru-RU/content/developers/apps/activating-beta-features-for-apps.md b/translations/ru-RU/content/developers/apps/activating-beta-features-for-apps.md index f349501d5f..25c83f6d3f 100644 --- a/translations/ru-RU/content/developers/apps/activating-beta-features-for-apps.md +++ b/translations/ru-RU/content/developers/apps/activating-beta-features-for-apps.md @@ -3,6 +3,8 @@ title: Activating beta features for apps intro: 'You can test new app features released in public beta for your {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s.' versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% warning %} diff --git a/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md b/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md index 8305fed871..05a771d379 100644 --- a/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md @@ -110,7 +110,7 @@ The example above uses the maximum expiration time of 10 minutes, after which th ```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" + "documentation_url": "{% data variables.product.doc_url_pre %}" } ``` diff --git a/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md index 8a297611c1..d878421fa4 100644 --- a/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/ru-RU/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### Introduction -This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. +This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts. 🙌 @@ -49,7 +49,7 @@ To get an idea of what your Checks API CI server will do when you've completed t ### Требования -Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details. +Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details. You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app. @@ -203,7 +203,7 @@ Great! You've told GitHub to create a check run. You can see the check run statu ### Step 1.4. Updating a check run -When your `create_check_run` method runs, it asks GitHub to create a new check run. When Github finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check. +When your `create_check_run` method runs, it asks GitHub to create a new check run. When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check. You'll want to update your event handler to look for the `created` action. While you're updating the event handler, you can add a conditional for the `rerequested` action. When someone re-runs a single test on GitHub by clicking the "Re-run" button, GitHub sends the `rerequested` check run event to your app. When a check run is `rerequested`, you'll want to start the process all over and create a new check run. diff --git a/translations/ru-RU/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/ru-RU/content/developers/apps/migrating-oauth-apps-to-github-apps.md index b0236b40ae..8b911fcf8c 100644 --- a/translations/ru-RU/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/ru-RU/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -52,7 +52,7 @@ GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/under #### Register a new GitHub App -Once you've decided to make the switch to Github Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). +Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). #### Determine the permissions your app requires @@ -62,7 +62,7 @@ In your GitHub App's settings, you can specify whether your app needs `No Access #### Subscribe to webhooks -After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a Github App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. +After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. #### Understand the different methods of authentication diff --git a/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md index b764ccce1e..61f9d01a55 100644 --- a/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/ru-RU/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,7 +42,7 @@ This callback request will send you a new access token and a new refresh token. { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" diff --git a/translations/ru-RU/content/developers/apps/suspending-a-github-app-installation.md b/translations/ru-RU/content/developers/apps/suspending-a-github-app-installation.md index bccc484a16..86da72d047 100644 --- a/translations/ru-RU/content/developers/apps/suspending-a-github-app-installation.md +++ b/translations/ru-RU/content/developers/apps/suspending-a-github-app-installation.md @@ -5,6 +5,8 @@ redirect_from: - /apps/managing-github-apps/suspending-a-github-app-installation versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% note %} diff --git a/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index a7c7bcf379..6a58d4c7a2 100644 --- a/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -14,7 +14,7 @@ versions: {% warning %} -If you offer a GitHub App in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate OAuth App to support this flow. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. +If you offer a {% data variables.product.prodname_github_app %} in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate {% data variables.product.prodname_oauth_app %} to support this flow. See "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endwarning %} @@ -24,7 +24,7 @@ Before a customer purchases your {% data variables.product.prodname_marketplace The customer completes the purchase by clicking **Complete order and begin installation**. -GitHub then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. +{% data variables.product.product_name %} then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. Read the `effective_date` and `marketplace_purchase` object from the `marketplace_purchase` webhook to determine which plan the customer purchased, when the billing cycle starts, and when the next billing cycle begins. @@ -34,27 +34,27 @@ See "[{% data variables.product.prodname_marketplace %} webhook events](/marketp ### Step 2. Установка -If your app is a GitHub App, GitHub prompts the customer to select which repositories the app can access when they purchase it. GitHub then installs the app on the account the customer selected and grants access to the selected repositories. +If your app is a {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} prompts the customer to select which repositories the app can access when they purchase it. {% data variables.product.product_name %} then installs the app on the account the customer selected and grants access to the selected repositories. -At this point, if you specified a **Setup URL** in your GitHub App settings, Github will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your GitHub App. +At this point, if you specified a **Setup URL** in your {% data variables.product.prodname_github_app %} settings, {% data variables.product.product_name %} will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your {% data variables.product.prodname_github_app %}. {% note %} -**Note:** The **Setup URL** is described as optional in GitHub App settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. +**Note:** The **Setup URL** is described as optional in {% data variables.product.prodname_github_app %} settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. {% endnote %} -If your app is an OAuth App, GitHub does not install it anywhere. Instead, GitHub redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). +If your app is an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} does not install it anywhere. Instead, {% data variables.product.product_name %} redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). -When a customer purchases an OAuth App, GitHub redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. +When a customer purchases an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. ### Step 3. Authorization When a customer purchases your app, you must send the customer through the OAuth authorization flow: -* If your app is a GitHub App, begin the authorization flow as soon as GitHub redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +* If your app is a {% data variables.product.prodname_github_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -* If your app is an OAuth App, begin the authorization flow as soon as GitHub redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/)." +* If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)." For either type of app, the first step is to redirect the customer to https://github.com/login/oauth/authorize. diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md index 2909630974..f7afa1c713 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -16,7 +16,7 @@ Repl.it is an online integrated development environment (IDE) that supports mult The first time the student clicks the button to visit Repl.it, the student must sign into Repl.it with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on Repl.it. -For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/misc/quick-start#the-repl-environment). +For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/repls/quick-start#the-repl-environment). For group assignments, students can use Repl.it Multiplayer to work collaboratively. For more information, see the [Repl.it Multiplayer](https://repl.it/site/multiplayer) website. diff --git a/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md index 359935372b..2df2bac24d 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -3,6 +3,7 @@ title: About Dependabot version updates intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the packages you use updated to the latest versions.' redirect_from: - /github/administering-a-repository/about-dependabot + - /github/administering-a-repository/about-github-dependabot - /github/administering-a-repository/about-github-dependabot-version-updates versions: free-pro-team: '*' @@ -14,9 +15,9 @@ versions: {% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on. -You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file in to your repository. The configuration file specifies the location of the manifest, or other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository, rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary. +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary. -When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to directly replace the outdated dependency with the new version. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)." +When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)." If you enable security updates, {% data variables.product.prodname_dependabot %} also raises pull requests to update vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." diff --git a/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md b/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md index c235c019e6..869f97b454 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-protected-branches.md @@ -82,12 +82,12 @@ After enabling required status checks, all required status checks must pass befo {% endnote %} -You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging. +You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up to date with the base branch before merging. | Type of required status check | Setting | Merge requirements | Considerations | | ----------------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Strict** | The **Require branches to be up-to-date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch. | -| **Loose** | The **Require branches to be up-to-date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. | +| **Strict** | The **Require branches to be up to date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch. | +| **Loose** | The **Require branches to be up to date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. | | **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes. | For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)." diff --git a/translations/ru-RU/content/github/administering-a-repository/about-securing-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/about-securing-your-repository.md index 3ff44718d7..1b85579495 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-securing-your-repository.md @@ -14,6 +14,8 @@ The first step to securing a repository is to set up who can see and modify your {% data variables.product.prodname_dotcom %} has a growing set of security features that help you keep your code secure. You can find these on the **Security** tab for your repository. +#### Available for all repositories + {% if currentVersion == "free-pro-team@latest" %} - **Security policy** @@ -43,15 +45,23 @@ Use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %} + +These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} + - **{% data variables.product.prodname_code_scanning_capc %} alerts** Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." - **Detected secrets** -View any secrets that - {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." - {% endif %} + {% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else if %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +- **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 "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +{% endif %} ### Exploring dependencies {% data variables.product.prodname_dotcom %}'s dependency graph allows you to explore: @@ -59,6 +69,6 @@ View any secrets that * Ecosystems and packages that your repository depends on * Repositories and packages that depend on your repository -You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. +You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. {% if currentVersion == "free-pro-team@latest" %}Enabling the dependency graph also enables {% data variables.product.prodname_dotcom %} to run dependency reviews of pull requests.{% endif %} You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." diff --git a/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md index 664c059198..e44763ea8d 100644 --- a/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md +++ b/translations/ru-RU/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -27,13 +27,13 @@ versions: {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png) 5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) 6. When you enable {% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. - ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png) + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} 4. To the right of " {% data variables.product.prodname_secret_scanning_caps %}", click **Enable**. ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-ghe.png) diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index e19203c066..5ff425d08d 100644 --- a/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -4,13 +4,12 @@ intro: "You can allow or disallow auto-merge for pull requests in your repositor product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' permissions: People with maintainer permissions can manage auto-merge for pull requests in a repository. --- -{% data reusables.pull_requests.auto-merge-release-phase %} - If you allow auto-merge for pull requests in your repository, people can configure individual pull requests in the repository to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Under "Merge button", select or deselect **Allow auto-merge**. ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) \ No newline at end of file +1. Under "Merge button", select or deselect **Allow auto-merge**. ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) diff --git a/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index 1a157fd60d..6c86bea636 100644 --- a/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -33,10 +33,15 @@ You can manage the security and analysis features for your {% if currentVersion {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} 4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. -{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} +**Note:** If you disable + + {% data variables.product.prodname_GH_advanced_security %}, both {% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail. + {% endnote %} + + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) {% endif %} diff --git a/translations/ru-RU/content/github/administering-a-repository/securing-your-repository.md b/translations/ru-RU/content/github/administering-a-repository/securing-your-repository.md index 5a92993859..df0cafb217 100644 --- a/translations/ru-RU/content/github/administering-a-repository/securing-your-repository.md +++ b/translations/ru-RU/content/github/administering-a-repository/securing-your-repository.md @@ -6,5 +6,6 @@ redirect_from: - /articles/securing-your-repository versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- diff --git a/translations/ru-RU/content/github/administering-a-repository/setting-repository-visibility.md b/translations/ru-RU/content/github/administering-a-repository/setting-repository-visibility.md index 9aa53e370b..032f85a010 100644 --- a/translations/ru-RU/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/ru-RU/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,7 +24,7 @@ We recommend reviewing the following caveats before you change the visibility of * If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %} * If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %} * Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} * {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %} diff --git a/translations/ru-RU/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/ru-RU/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md index 625163c0d8..41588a5516 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md +++ b/translations/ru-RU/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md @@ -33,14 +33,18 @@ If you're using a GPG key that matches your committer identity and your verified Comment: GitHub key Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? ``` -7. Enter `O` to save your selections. +7. Enter `O` to confirm your selections. 8. Enter your key's passphrase. -9. Enter `gpg --armor --export GPG key ID`, substituting in the GPG key ID you'd like to use. In the following example, the GPG key ID is `3AA5C34371567BD2`: +9. Enter `gpg> save` to save the changes + ```shell + $ gpg> save + ``` +10. Enter `gpg --armor --export GPG key ID`, substituting in the GPG key ID you'd like to use. In the following example, the GPG key ID is `3AA5C34371567BD2`: ```shell $ gpg --armor --export 3AA5C34371567BD2 # Prints the GPG key, in ASCII armor format ``` -10. Upload the GPG key by [adding it to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account). +11. Upload the GPG key by [adding it to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account). ### Дополнительная литература diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index 378da8df6d..ebdf5698ed 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -4,10 +4,9 @@ intro: 'You can increase development velocity by enabling auto-merge for a pull product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' --- -{% data reusables.pull_requests.auto-merge-release-phase %} - ### About auto-merge If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks. diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index 0621b60adc..3e1b381cdf 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -9,7 +9,6 @@ versions: github-ae: '*' --- - ### About pull request merges In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. By default, any pull request can be merged at any time, unless the head branch is in conflict with the base branch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index 5fd954aedf..968d300f7c 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -23,7 +23,7 @@ When someone with admin or owner permissions has enabled required reviews, they {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If a team has enabled code review assignments, the individual approvals won't satisfy the requirement for code owner approval in a protected branch. For more information, see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}. diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index 20afd7d49b..d14b497650 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -22,7 +22,7 @@ If {% data variables.product.prodname_code_scanning %} finds a potential vulnera To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/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)." +To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." ### About {% data variables.product.prodname_codeql %} diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index ba9b492ab9..046e050b33 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -18,7 +18,7 @@ You can run {% data variables.product.prodname_code_scanning %} within {% data v This article relates to 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)." +Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} @@ -26,7 +26,7 @@ Before you can configure {% data variables.product.prodname_code_scanning %} for ### 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_. +{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added 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) @@ -134,7 +134,7 @@ The default {% data variables.product.prodname_codeql_workflow %} file contains {% 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. +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 set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix. ```yaml jobs: diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index f2d7f5abc3..b3d137c1a7 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -134,19 +134,22 @@ Attempts to build the code for the compiled languages C/C++, C#, and Java. For t Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_location %}. -| Flag | Required | Input value | -| -------------------------------- |:--------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--repository` | ✓ | 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. | +| Flag | Required | Input value | +| ---------------------------------- |:--------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `--repository` | ✓ | 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. | +| `--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. | +| `--threads` | | Number of threads to use when running queries. The default is to use all available cores. | +| `--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. | #### `загрузить` diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md index 8ddfc0b163..d7994759b0 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md @@ -17,7 +17,7 @@ versions: ### About the {% data variables.product.prodname_codeql_workflow %} and compiled languages -You enable {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.product.prodname_codeql_workflow %}. 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)." +You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.product.prodname_codeql_workflow %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} For general information about configuring diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md index f5742510b7..3c5f11b678 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md @@ -14,7 +14,7 @@ versions: {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %} {% link_in_list /about-code-scanning %} {% link_in_list /triaging-code-scanning-alerts-in-pull-requests %} - {% link_in_list /enabling-code-scanning-for-a-repository %} + {% link_in_list /setting-up-code-scanning-for-a-repository %} {% link_in_list /managing-code-scanning-alerts-for-your-repository %} {% link_in_list /configuring-code-scanning %} {% link_in_list /configuring-the-codeql-workflow-for-compiled-languages %} diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index a0c5739aa3..429eb54c73 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -16,7 +16,7 @@ redirect_from: ### About alerts from {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[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)." +You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." @@ -28,7 +28,7 @@ Each alert highlights a problem with the code and the name of the tool that iden ![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) -If you enable {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information. +If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information. When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users. @@ -65,7 +65,7 @@ Closing an alert is a way to resolve an alert that you don't think needs to be f ### Dismissing or deleting alerts -There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have enabled a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have enabled {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab. +There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab. Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab. @@ -127,5 +127,5 @@ If a project has multiple alerts that you want to dismiss for the same reason, y ### Дополнительная литература - "[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)" -- "[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)" +- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" - "[About integration with {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)" diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 0b377144c3..061fe37cdd 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -24,7 +24,7 @@ If you use a continuous integration or continuous delivery/deployment (CI/CD) sy {% 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)." +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 "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-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. diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 5b6f36c087..278472985b 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -97,7 +97,6 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr | `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). | -| `suppressions[].state` | **Optional.** When the `state` is set to `accepted`, {% data variables.product.prodname_code_scanning %} will update the state of the result to `Closed` on {% data variables.product.prodname_dotcom %}. | #### `location` object diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md new file mode 100644 index 0000000000..08ca6faab6 --- /dev/null +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -0,0 +1,117 @@ +--- +title: Setting up code scanning for a repository +shortTitle: Setting up code scanning +intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.' +redirect_from: + - /github/managing-security-vulnerabilities/configuring-automated-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} + +### Options for setting up {% data variables.product.prodname_code_scanning %} + +You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to 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 %} + +### Setting up {% 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. 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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/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 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. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." + +### 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. 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. + +### Дальнейшие шаги + +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](/github/finding-security-vulnerabilities-and-errors-in-your-code/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. + + ![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 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. + +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, and this branch hasn't been analyzed. + + To the right of "Code scanning", click **Set up code scanning**. + + ![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 %}. + +### Дальнейшие шаги + +After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: + +- You can customize how {% data variables.product.prodname_code_scanning %} scans the code in your 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 set up {% data variables.product.prodname_code_scanning %}. 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)." +- 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/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index b2eded39f1..626cd99e0d 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -15,7 +15,7 @@ versions: 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](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, 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 notices and the check succeeds. If your pull request targets a protected branch that has been enabled for {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." +If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, 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 notices and the check succeeds. 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 you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." ![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md index 46af6876b3..96ed07f92d 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md @@ -75,7 +75,7 @@ When ### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% 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 %} +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](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} By default, we notify people with admin permissions in the affected repositories about new @@ -89,6 +89,11 @@ We send security alerts to people with admin permissions in the affected reposit {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} 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" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %} +{% if currentVersion == "free-pro-team@latest" %} +You can also see all the +{% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in 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#viewing-your-vulnerable-repositories)." +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} ### Дополнительная литература diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md index f43190ddc3..bc00b8d653 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -24,7 +24,7 @@ The severity level is one of four possible levels defined in the [Common Vulnera - Высокий - Critical -The {% data variables.product.prodname_advisory_database %} uses CVSS version 3.0 standards and the CVSS levels described above. {% data variables.product.product_name %} doesn't publish CVSS scores. +The {% data variables.product.prodname_advisory_database %} uses CVSS version 3.0 standards and the CVSS levels described above. {% data reusables.repositories.github-security-lab %} @@ -41,24 +41,39 @@ The database is also accessible using the GraphQL API. For more information, see {% endnote %} ### Searching the {% data variables.product.prodname_advisory_database %} -You can search the database, and use qualifiers to narrow your search to advisories created on a certain date, in a specific ecosystem, or in a particular library. + +You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Пример | -| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | -| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | -| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | -| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | -| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | -| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | -| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | -| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | -| `created:YYYY-MM-DD` | [**created:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2019-10-31) will show only advisories created on this date. | -| `updated:YYYY-MM-DD` | [**updated:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2019-10-31) will show only advisories updated on this date. | +| Qualifier | Пример | +| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `GHSA-ID` | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | +| `CVE-ID` | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | +| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | +| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | +| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | +| `cwe:ID` | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | +| `credit:USERNAME` | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | +| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | +| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | +| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | +| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | +| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | +| `created:YYYY-MM-DD` | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | +| `updated:YYYY-MM-DD` | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. | + +### Viewing your vulnerable repositories + +For any vulnerability in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories have a {% data variables.product.prodname_dependabot %} alert for that vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)." + +1. Navigate to https://github.com/advisories. +2. Click an advisory. +3. At the top of the advisory page, click **Dependabot alerts**. ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png) +4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) +5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name. ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index 4b001281e3..a8bba109a0 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -12,6 +12,8 @@ versions: {% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." +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 %} usage beyond the amounts including with your account. 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)." + Minutes reset every month, while storage usage does not. | Product | Storage | Minutes (per month) | diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 4674dc6c72..62682cdcbc 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.package_registry.container-registry-beta-billing-note %} +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_registry %} usage beyond the amounts including with your account. 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 transfer resets every month, while storage usage does not. | Product | Storage | Data transfer (per month) | diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 8ae1262da6..d60c00f961 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} 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)." +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 %} usage beyond the amounts including with your account. 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)." + As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and creates workflow artifacts that increase your storage usage for the month from 1.9GB to 2.1GB, you will use slightly more storage than the 2GB your product includes. Because you have not enabled overages, your next attempt to create a workflow artifact will fail. You will not receive a bill for the 0.1GB overage that month. However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue. diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index a89aca74c9..b7e1e4fde1 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} 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)." +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_registry %} usage beyond the amounts including with your account. 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)." + As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and publishes a new version of a private package that increases your storage usage for the month from 1.9GB to 2.1GB, publishing the version will use slightly more than the 2GB your product includes. Because you have not enabled overages, your next attempt to publish a version of the package will fail. You will not receive a bill for the 0.1GB overage that month. However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue. diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 0107a236ec..ec45c2dea3 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -23,8 +23,13 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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. +The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. +{% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@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.{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![{% data variables.product.prodname_GH_advanced_security %} features](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) {% endif %} @@ -42,24 +47,21 @@ You can enable or disable features for all repositories. {% if currentVersion == 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)." 1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) {% endif %} 2. Optionally, enable the feature by default for new repositories in your organization. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) {% endif %} -1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. - {% if currentVersion == "free-pro-team@latest" %} +3. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) {% endif %} @@ -68,10 +70,9 @@ You can enable or disable features for all repositories. {% if currentVersion == 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)." 1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories {% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization. - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![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 %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) {% endif %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 8c0f383a5c..a5ee0f19f0 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -70,7 +70,7 @@ In addition to managing organization-level settings, organization owners have ad {% 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** |{% if currentVersion == "free-pro-team@latest" %} +| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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** | @@ -150,8 +150,8 @@ In this section, you can find the repository permission levels required for secu | Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | | [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/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** | -| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** | +| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% 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 | | | | | **X** | | [View dependency reviews](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | [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** | diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md new file mode 100644 index 0000000000..ea9b3d4b19 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md @@ -0,0 +1,40 @@ +--- +title: Connecting an Azure subscription to your enterprise +intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the included amounts for your enterprise.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise +versions: + free-pro-team: '*' +--- + +### About Azure subscriptions and {% data variables.product.product_name %} + +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 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) and "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." + +After you connect an Azure subscription, you can also manage your spending limit. For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)" and "[Managing your spending limit for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)." + +### Connecting your Azure subscription to your enterprise account + +To connect your Azure subscription, you must have owner permissions to the subscription. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Payment Information", click **Add Azure Subscription**. +1. To sign in to your Microsoft account, follow the prompts. +1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**. +1. Under "Select a subscription", select the Azure Subscription ID that you want to connect to your enterprise. +1. Click **Connect**. + +### Disconnecting your Azure subscription from your enterprise account + +After you disconnect your Azure subscription from your enterprise account, your usage can no longer exceed the amounts included with your plan. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. +1. Review the prompt, then click **Remove**. 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 4dae4a37df..a0f04ad09c 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 @@ -18,6 +18,7 @@ versions: {% link_in_list /about-enterprise-accounts %} {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %} {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %} + {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %} {% topic_link_in_list /managing-users-in-your-enterprise %} {% link_in_list /roles-in-an-enterprise %} {% link_in_list /inviting-people-to-manage-your-enterprise %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md index 6114d2f526..635863a362 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise.md @@ -31,7 +31,7 @@ Enterprise owners have complete control over the enterprise and can take every a Enterprise owners cannot access organization settings or content unless they are made an organization owner or given direct access to an organization-owned repository. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. -You can add as many enterprise owners as you'd like to your enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. +An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. ### Enterprise members @@ -52,7 +52,7 @@ Billing managers only have access to your enterprise's billing settings. Billing - View a list of billing managers - Add or remove other billing managers -Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}. +Billing managers will only consume a license if they are an owner or member of at least one organization within the enterprise. Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}. ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 3b2c0ceb76..14d76e4172 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -15,6 +15,8 @@ versions: Enterprise accounts are currently available to {% data variables.product.prodname_enterprise %} customers paying by invoice. Billing for all of the organizations and {% data variables.product.prodname_ghe_server %} instances connected to your enterprise account are aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services (including paid licenses in organizations, {% data variables.large_files.product_name_long %} data packs, and subscriptions for {% data variables.product.prodname_marketplace %} apps). +{% if currentVersion == "free-pro-team@latest" %}{% 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)."{% endif %} + For more information about managing billing managers, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." ### Viewing the subscription and usage for your enterprise account diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index 708e5d2d8c..c89d652fd2 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -50,7 +50,7 @@ The repository owner has full control of the repository. In addition to the acti | Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | | Archive the repository | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} | Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | -| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" | +| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} | Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %} ### Collaborator access for a repository owned by a user account diff --git a/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index 0d52fe4c3d..32161f7478 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -25,8 +25,6 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages % {% 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 %} @@ -36,6 +34,8 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages % {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% 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 diff --git a/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site.md b/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site.md index cd654b9311..042afb1704 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site.md +++ b/translations/ru-RU/content/github/working-with-github-pages/creating-a-github-pages-site.md @@ -20,8 +20,6 @@ versions: {% 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 %} @@ -33,6 +31,8 @@ versions: {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% data reusables.pages.navigate-site-repo %} {% data reusables.pages.decide-publishing-source %} 3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source. diff --git a/translations/ru-RU/content/rest/overview/libraries.md b/translations/ru-RU/content/rest/overview/libraries.md index 2d0f25d9c9..51935046da 100644 --- a/translations/ru-RU/content/rest/overview/libraries.md +++ b/translations/ru-RU/content/rest/overview/libraries.md @@ -57,7 +57,7 @@ Library name | Repository | |---|---| **NodeJS GitHub library**| [pksunkara/octo ### Julia -Library name | Repository | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl) +Library name | Repository | |---|---| **GitHub.jl**|[WestleyArgentum/GitHub.jl](https://github.com/WestleyArgentum/GitHub.jl) ### OCaml @@ -65,11 +65,11 @@ Library name | Repository | |---|---| **ocaml-github**|[mirage/ocaml-github](htt ### Perl -Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub) +Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub) ### PHP -Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI) +Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GitHubAPI](https://github.com/FlexyProject/GitHubAPI) ### Python diff --git a/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md b/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md index a9f8c69965..5b1e02fa2e 100644 --- a/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md @@ -129,7 +129,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar > { > "message": "Bad credentials", -> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -141,7 +141,7 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f > 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" +> "documentation_url": "{% data variables.product.doc_url_pre %}" > } ``` @@ -358,7 +358,7 @@ If you exceed the rate limit, an error response returns: > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#rate-limiting" > } ``` @@ -403,7 +403,7 @@ If your application triggers this rate limit, you'll receive an informative resp > { > "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" +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#abuse-rate-limits" > } ``` diff --git a/translations/ru-RU/content/rest/reference/repos.md b/translations/ru-RU/content/rest/reference/repos.md index f779c766b2..7a50afa9db 100644 --- a/translations/ru-RU/content/rest/reference/repos.md +++ b/translations/ru-RU/content/rest/reference/repos.md @@ -141,7 +141,7 @@ Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth- ### Inactive deployments -When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. +When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository to the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status. You can communicate that a transient environment no longer exists by setting its `state` to `inactive`. Setting the `state` to `inactive` shows the deployment as `destroyed` in {% data variables.product.prodname_dotcom %} and removes access to it. diff --git a/translations/ru-RU/data/reusables/actions/enterprise-beta.md b/translations/ru-RU/data/reusables/actions/enterprise-beta.md index b10237e282..0c674122af 100644 --- a/translations/ru-RU/data/reusables/actions/enterprise-beta.md +++ b/translations/ru-RU/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,12 @@ {% if enterpriseServerVersions contains currentVersion 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 "[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)." +**Note:** {% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. The beta has ended. {% data variables.product.prodname_actions %} is now generally available in {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +
+ +- For more information about upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." +- For more information about configuring {% data variables.product.prodname_actions %} after you upgrade, see the [documentation for {% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server). {% endnote %} {% endif %} diff --git a/translations/ru-RU/data/reusables/actions/enterprise-common-prereqs.md b/translations/ru-RU/data/reusables/actions/enterprise-common-prereqs.md index ee9ba1dca8..3a9923ae8e 100644 --- a/translations/ru-RU/data/reusables/actions/enterprise-common-prereqs.md +++ b/translations/ru-RU/data/reusables/actions/enterprise-common-prereqs.md @@ -1,4 +1,4 @@ -* {% data reusables.actions.enterprise-hardware-considerations %} +* Review the hardware requirements for {% data variables.product.prodname_actions %}. 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#review-hardware-considerations)." * TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." {% note %} diff --git a/translations/ru-RU/data/reusables/actions/enterprise-hardware-considerations.md b/translations/ru-RU/data/reusables/actions/enterprise-hardware-considerations.md index 24c077bbae..98ac65f438 100644 --- a/translations/ru-RU/data/reusables/actions/enterprise-hardware-considerations.md +++ b/translations/ru-RU/data/reusables/actions/enterprise-hardware-considerations.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "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)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. +If you {% if currentVersion == "enterprise-server@2.22" %} configured the beta of{% else %} configure{% endif %} {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, we recommend that you provision additional CPU and memory resources. The additional resources you need to provision depend on the number of workflows your users run concurrently, and the overall levels of activity for your instance. diff --git a/translations/ru-RU/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/ru-RU/data/reusables/advanced-security/note-org-enable-uses-seats.md index 48f3c5a99a..733e8e8a97 100644 --- a/translations/ru-RU/data/reusables/advanced-security/note-org-enable-uses-seats.md +++ b/translations/ru-RU/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -1,7 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. This option controls access to all {% data variables.product.prodname_advanced_security %} features including {% if currentVersion == "free-pro-team@latest" %}dependency review,{% endif %} {% data variables.product.prodname_code_scanning %}, and {% data variables.product.prodname_secret_scanning %}. {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/code-scanning/enabling-options.md b/translations/ru-RU/data/reusables/code-scanning/enabling-options.md index 3ef6731b26..bbbd1a7893 100644 --- a/translations/ru-RU/data/reusables/code-scanning/enabling-options.md +++ b/translations/ru-RU/data/reusables/code-scanning/enabling-options.md @@ -15,7 +15,7 @@ - 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"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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"). @@ -25,7 +25,7 @@ - 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 %}"). + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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 %}"). 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 72facd7034..6ddfcb36e5 100644 --- a/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md @@ -8,7 +8,7 @@ The following table shows, for each package manager: | --------------------------------- | ---------------- | ------------------------- |:--------------------:|:---------:| | Средство увязки программ в пакеты | `bundler` | v1 | | **✓** | | Cargo | `cargo` | v1 | **✓** | | -| Composer | `composer` | v1,v2 | **✓** | | +| Composer | `composer` | v1, v2 | **✓** | | | Докер | `докер` | v1 | **✓** | | | Elixir | `mix` | v1 | **✓** | | | Elm | `elm` | v0.18, v0.19 | **✓** | | @@ -17,7 +17,7 @@ The following table shows, for each package manager: | Go modules | `gomod` | v1 | **✓** | **✓** | | Gradle | `gradle` | see (A) below | **✓** | | | Maven | `maven` | see (B) below | **✓** | | -| npm | `npm` | v6 | **✓** | | +| npm | `npm` | v6, v7 | **✓** | | | NuGet | `nuget` | <= 4.8.
see (C) below | **✓** | | | pip | `pip` | v20 | | | | pipenv | `pip` | <= 2018.11.26 | | | diff --git a/translations/ru-RU/data/reusables/desktop/choose-clone-repository.md b/translations/ru-RU/data/reusables/desktop/choose-clone-repository.md index 45deab6ea4..41f4b6a914 100644 --- a/translations/ru-RU/data/reusables/desktop/choose-clone-repository.md +++ b/translations/ru-RU/data/reusables/desktop/choose-clone-repository.md @@ -1 +1,13 @@ 1. In the **File** menu, click **Clone Repository**. + + {% mac %} + + ![Clone menu option in the Mac app](/assets/images/help/desktop/clone-file-menu-mac.png) + + {% endmac %} + + {% windows %} + + ![Clone menu option in the Windows app](/assets/images/help/desktop/clone-file-menu-windows.png) + + {% endwindows %} diff --git a/translations/ru-RU/data/reusables/desktop/choose-local-path.md b/translations/ru-RU/data/reusables/desktop/choose-local-path.md new file mode 100644 index 0000000000..8bf8a7ac5f --- /dev/null +++ b/translations/ru-RU/data/reusables/desktop/choose-local-path.md @@ -0,0 +1,13 @@ +1. Click **Choose...** and navigate to a local path where you want to clone the repository. + + {% mac %} + + ![The choose button](/assets/images/help/desktop/clone-choose-button-mac.png) + + {% endmac %} + + {% windows %} + + ![The choose button](/assets/images/help/desktop/clone-choose-button-win.png) + + {% endwindows %} diff --git a/translations/ru-RU/data/reusables/desktop/click-clone.md b/translations/ru-RU/data/reusables/desktop/click-clone.md new file mode 100644 index 0000000000..d291246ebf --- /dev/null +++ b/translations/ru-RU/data/reusables/desktop/click-clone.md @@ -0,0 +1,14 @@ +1. Click **Clone**. + + {% mac %} + + ![The clone button](/assets/images/help/desktop/clone-button-mac.png) + + {% endmac %} + + {% windows %} + + ![The clone button](/assets/images/help/desktop/clone-button-win.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/desktop/cloning-location-tab.md b/translations/ru-RU/data/reusables/desktop/cloning-location-tab.md index 8752592c0e..e4610d9f88 100644 --- a/translations/ru-RU/data/reusables/desktop/cloning-location-tab.md +++ b/translations/ru-RU/data/reusables/desktop/cloning-location-tab.md @@ -1 +1,13 @@ 1. Click the tab that corresponds to the location of the repository you want to clone. You can also click **URL** to manually enter the repository location. + + {% mac %} + + ![Location tabs in the Clone a repository menu](/assets/images/help/desktop/choose-repository-location-mac.png) + + {% endmac %} + + {% windows %} + + ![Location tabs in the Clone a repository menu](/assets/images/help/desktop/choose-repository-location-win.png) + + {% endwindows %} diff --git a/translations/ru-RU/data/reusables/desktop/cloning-repository-list.md b/translations/ru-RU/data/reusables/desktop/cloning-repository-list.md index 37d26e3039..97a7f7a894 100644 --- a/translations/ru-RU/data/reusables/desktop/cloning-repository-list.md +++ b/translations/ru-RU/data/reusables/desktop/cloning-repository-list.md @@ -1 +1,14 @@ 1. Choose the repository you want to clone from the list. + + + {% mac %} + + ![Clone a repository list](/assets/images/help/desktop/clone-a-repository-list-mac.png) + + {% endmac %} + + {% windows %} + + ![Clone a repository list](/assets/images/help/desktop/clone-a-repository-list-win.png) + + {% endwindows %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/desktop/fork-type-prompt.md b/translations/ru-RU/data/reusables/desktop/fork-type-prompt.md new file mode 100644 index 0000000000..1067dab748 --- /dev/null +++ b/translations/ru-RU/data/reusables/desktop/fork-type-prompt.md @@ -0,0 +1,42 @@ +1. If you plan to use this fork for contributing to the original upstream repository, click **To contribute to the parent project**. + + {% mac %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/mac-fork-options-prompt.png) + + {% endmac %} + + {% windows %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/windows-fork-options-prompt.png) + + {% endwindows %} + +2. If you plan to use this fork for a project not connected to the upstream, click **For my own purposes**. + + {% mac %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/mac-fork-own-purposes.png) + + {% endmac %} + + {% windows %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/windows-fork-own-purposes.png) + + {% endwindows %} + +3. Click **Continue**. + + {% mac %} + + ![The continue button](/assets/images/help/desktop/mac-forking-continue.png) + + {% endmac %} + + {% windows %} + + ![The continue button](/assets/images/help/desktop/windows-forking-continue.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/desktop/open-repository-settings.md b/translations/ru-RU/data/reusables/desktop/open-repository-settings.md new file mode 100644 index 0000000000..5e298edc85 --- /dev/null +++ b/translations/ru-RU/data/reusables/desktop/open-repository-settings.md @@ -0,0 +1,14 @@ +1. Open the **Repository** menu, then click **Repository settings...**. + + {% mac %} + + ![Repository settings menu option in the Mac app](/assets/images/help/desktop/mac-repository-settings.png) + + {% endmac %} + + {% windows %} + + ![Repository settings menu option in the Windows app](/assets/images/help/desktop/windows-repository-settings.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/desktop/select-fork-behavior.md b/translations/ru-RU/data/reusables/desktop/select-fork-behavior.md new file mode 100644 index 0000000000..05785064e3 --- /dev/null +++ b/translations/ru-RU/data/reusables/desktop/select-fork-behavior.md @@ -0,0 +1,28 @@ +1. Click **Fork behavior**, then select how you want to use the fork. + + {% mac %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-menu-contribute.png) + + {% endmac %} + + {% windows %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-menu-contribute.png) + + {% endwindows %} + +2. Click **Save**. + + {% mac %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-save.png) + + {% endmac %} + + {% windows %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-save.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md b/translations/ru-RU/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md new file mode 100644 index 0000000000..63fa9473e7 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md @@ -0,0 +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 including with your account. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/payment-information-tab.md b/translations/ru-RU/data/reusables/enterprise-accounts/payment-information-tab.md new file mode 100644 index 0000000000..4de0966ad7 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/payment-information-tab.md @@ -0,0 +1 @@ +1. Under "Billing", click **Payment information**. diff --git a/translations/ru-RU/data/reusables/enterprise_installation/about-adjusting-resources.md b/translations/ru-RU/data/reusables/enterprise_installation/about-adjusting-resources.md new file mode 100644 index 0000000000..2d6c2fe4e6 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise_installation/about-adjusting-resources.md @@ -0,0 +1 @@ +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)." diff --git a/translations/ru-RU/data/reusables/enterprise_installation/aws-supported-instance-types.md b/translations/ru-RU/data/reusables/enterprise_installation/aws-supported-instance-types.md index 5cf0c50693..652361d9ff 100644 --- a/translations/ru-RU/data/reusables/enterprise_installation/aws-supported-instance-types.md +++ b/translations/ru-RU/data/reusables/enterprise_installation/aws-supported-instance-types.md @@ -1,37 +1,13 @@ -{% data variables.product.prodname_ghe_server %} is supported on the following EC2 instance types. For more information, see [the AWS EC2 instance type overview page](http://aws.amazon.com/ec2/instance-types/). +{% data variables.product.prodname_ghe_server %} is supported on the following EC2 instance sizes. For more information, see [the AWS EC2 instance type overview page](http://aws.amazon.com/ec2/instance-types/). -| EC2 instance type | Model | -| ----------------- | ---------------------------------- | -| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | - -| EC2 instance type | Model | -| ----------------- | ---------------------------------- | -| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | - -| EC2 instance type | Model | -| ----------------- | -------------------------------------------------------------------- | -| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | - -| EC2 instance type | Model | -| ----------------- | --------------------- | -| M3 | m3.xlarge, m3.2xlarge | - -| EC2 instance type | Model | -| ----------------- | ----------------------------------------------------------- | -| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | - -| EC2 instance type | Model | -| ----------------- | --------------------------------------------------------------------- | -| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | - -| EC2 instance type | Model | -| ----------------- | -------------------------------------------------------------------- | -| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | - -| EC2 instance type | Model | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} - -| EC2 instance type | Model | -| ----------------- | ------------------------ | -| X1 | x1.16xlarge, x1.32xlarge | +| Тип | Size | +|:--- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | +| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | +| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | +| M3 | m3.xlarge, m3.2xlarge | +| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | +| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | +| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | +| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} +| X1 | x1.16xlarge, x1.32xlarge | diff --git a/translations/ru-RU/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/ru-RU/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index 1bdc5adca7..ec895f314d 100644 --- a/translations/ru-RU/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/ru-RU/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,6 +1,5 @@ - [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %} -- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %} -- [Optional features](#optional-features){% endif %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %} - [Storage](#storage) - [CPU and memory](#cpu-and-memory) @@ -8,20 +7,7 @@ We recommend different hardware configurations depending on the number of user licenses for {% data variables.product.product_location %}. If you provision more resources than the minimum requirements, your instance will perform and scale better. -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations. - -- You must configure at least one runner for {% data variables.product.prodname_actions %} workflows. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." -- You must configure external blob storage. 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)." -- You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} 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 | Additional vCPUs | Additional memory | - |:----------------------- | ----------------:| -----------------:| - | Light testing | 4 | 30.5 GB | - | 25 | 8 | 61 GB | - | 35 | 16 | 122 GB | - | 100 | 32 | 244 GB | - -{% endif %} +{% data reusables.enterprise_installation.hardware-rec-table %} #### Storage @@ -31,7 +17,7 @@ Your instance requires a persistent data disk separate from the root disk. For m {% if currentVersion ver_gt "enterprise-server@2.21" %} -If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. 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)." +To configure{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you must provide external blob storage. 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)." {% endif %} @@ -39,7 +25,7 @@ You can resize your instance's root disk by building a new instance or using an #### 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. +The CPU and memory resources that {% data variables.product.prodname_ghe_server %} requires depend on the levels of activity for users, automations, and integrations. {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data reusables.actions.enterprise-hardware-considerations %}{% endif %} {% data reusables.enterprise_installation.increasing-cpus-req %} diff --git a/translations/ru-RU/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/ru-RU/data/reusables/enterprise_installation/hardware-rec-table.md index a9ffb7473a..a7310c66fc 100644 --- a/translations/ru-RU/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/ru-RU/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,20 +1,20 @@ -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}." +**Note**: If you joined the beta for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} and enabled the features, your instance requires additional hardware resources. 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)." {% endnote %} {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -| User licenses | vCPUs | Memory | Attached storage | Root storage | -|:------------------------------ | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| ------------:| -| Trial, demo, or 10 light users | 2
or [**4**](#optional-features) | 16 GB
or [**32 GB**](#optional-features) | 100 GB
or [**150 GB**](#optional-features) | 200 GB | -| 10 to 3,000 | 4
or [**8**](#optional-features) | 32 GB
or [**48 GB**](#optional-features) | 250 GB
or [**300 GB**](#optional-features) | 200 GB | -| 3,000 to 5000 | 8
or [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | -| 5,000 to 8000 | 12
or [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | -| 8,000 to 10,000+ | 16
or [**20**](#optional-features) | 128 GB
or [**160 GB**](#optional-features) | 1000 GB | 200 GB | +| User licenses | vCPUs | Memory | Attached storage | Root storage | +|:------------------------------ | -----:| ------:| ----------------:| ------------:| +| Trial, demo, or 10 light users | 4 | 32 GB | 150 GB | 200 GB | +| 10 to 3,000 | 8 | 48 GB | 300 GB | 200 GB | +| 3,000 to 5000 | 12 | 64 GB | 500 GB | 200 GB | +| 5,000 to 8000 | 16 | 96 GB | 750 GB | 200 GB | +| 8,000 to 10,000+ | 20 | 160 GB | 1000 GB | 200 GB | {% else %} @@ -28,22 +28,20 @@ {% endif %} -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)." +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +If you plan to configure {% data variables.product.prodname_actions %} for your instance, you should provision additional resources. You must also configure at least one self-hosted runner to execute workflows. 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)." + +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} #### Beta features in {% data variables.product.prodname_ghe_server %} 2.22 -You can sign up for beta features available in {% data variables.product.prodname_ghe_server %} 2.22 such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [release notes for the 2.22 series](https://enterprise.github.com/releases/series/2.22#release-2.22.0) on the {% data variables.product.prodname_enterprise %} website. +{% data variables.product.prodname_ghe_server %} 2.22 offered features in beta, such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [{% data variables.product.prodname_ghe_server %} 2.22 release notes](/enterprise-server@2.22/admin/release-notes#2.22.0). -If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". - -{% elsif currentVersion ver_gt "enterprise-server@2.22" %} - -#### Optional features - -You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. 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)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." - -If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". +If you enabled beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)". {% endif %} diff --git a/translations/ru-RU/data/reusables/gated-features/auto-merge.md b/translations/ru-RU/data/reusables/gated-features/auto-merge.md index 72a58ba07d..acfb4dddff 100644 --- a/translations/ru-RU/data/reusables/gated-features/auto-merge.md +++ b/translations/ru-RU/data/reusables/gated-features/auto-merge.md @@ -1 +1 @@ -Auto-merge for pull requests 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" %}{% data reusables.gated-features.more-info %}{% endif %} \ No newline at end of file +Auto-merge for pull requests 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 %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/ru-RU/data/reusables/gated-features/code-scanning.md b/translations/ru-RU/data/reusables/gated-features/code-scanning.md index 69e6abf27f..35598cce54 100644 --- a/translations/ru-RU/data/reusables/gated-features/code-scanning.md +++ b/translations/ru-RU/data/reusables/gated-features/code-scanning.md @@ -1 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled. +{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository. +{%- else %} +{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} 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 37caf3e2cc..103252d436 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 @@ -1,8 +1,8 @@ -| Virtual environment | YAML workflow label | -| -------------------- | ---------------------------------- | -| Windows Server 2019 | `windows-latest` or `windows-2019` | -| Ubuntu 20.04 | `ubuntu-20.04` | -| Ubuntu 18.04 | `ubuntu-latest` or `ubuntu-18.04` | -| Ubuntu 16.04 | `ubuntu-16.04` | -| macOS Big Sur 11.0 | `macos-11.0` | -| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | +| Virtual environment | YAML workflow label | +| -------------------- | -------------------------------------------- | +| Windows Server 2019 | `windows-latest` or `windows-2019` | +| Ubuntu 20.04 | `ubuntu-latest` (see note) or `ubuntu-20.04` | +| Ubuntu 18.04 | `ubuntu-latest` (see note) or `ubuntu-18.04` | +| Ubuntu 16.04 | `ubuntu-16.04` | +| macOS Big Sur 11.0 | `macos-11.0` | +| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | diff --git a/translations/ru-RU/data/reusables/github-actions/ubuntu-runner-preview.md b/translations/ru-RU/data/reusables/github-actions/ubuntu-runner-preview.md index 1a3636e0e1..6eb91edc13 100644 --- a/translations/ru-RU/data/reusables/github-actions/ubuntu-runner-preview.md +++ b/translations/ru-RU/data/reusables/github-actions/ubuntu-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The Ubuntu 20.04 virtual environment is currently provided as a preview only. The `ubuntu-latest` YAML workflow label still uses the Ubuntu 18.04 virtual environment. +**Note:** The `ubuntu-latest` label is currently being migrated from the Ubuntu 18.04 virtual environment to Ubuntu 20.04. Specifying the `ubuntu-latest` label during the migration might use either virtual environment. To explicitly use Ubuntu 20.04 or Ubuntu 18.04, specify `ubuntu-20.04` or `ubuntu-18.04`. When the migration is complete, `ubuntu-latest` will use the Ubuntu 20.04 virtual environment. For more information about the migration, see "[Ubuntu-latest workflows will use Ubuntu-20.04](https://github.com/actions/virtual-environments/issues/1816)." {% endnote %} diff --git a/translations/ru-RU/data/reusables/organizations/organizations_include.md b/translations/ru-RU/data/reusables/organizations/organizations_include.md index da902c12ed..766b2394dc 100644 --- a/translations/ru-RU/data/reusables/organizations/organizations_include.md +++ b/translations/ru-RU/data/reusables/organizations/organizations_include.md @@ -6,3 +6,4 @@ Organizations include: - [Nested teams that reflect your company or group's structure](/articles/about-teams) with cascading access permissions and mentions{% if currentVersion != "github-ae@latest" %} - The ability for organization owners to view members' [two-factor authentication (2FA) status](/articles/about-two-factor-authentication) - The option to [require all organization members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization){% endif %} +{% if currentVersion == "free-pro-team@latest" %}- The option to purchase a license for {% data variables.product.prodname_GH_advanced_security %} and use the features on private repositories. {% data reusables.advanced-security.more-info-ghas %}{% endif %} diff --git a/translations/ru-RU/data/reusables/pages/new-or-existing-repo.md b/translations/ru-RU/data/reusables/pages/new-or-existing-repo.md index 4fdcdaf871..bfb5ba3b47 100644 --- a/translations/ru-RU/data/reusables/pages/new-or-existing-repo.md +++ b/translations/ru-RU/data/reusables/pages/new-or-existing-repo.md @@ -1,3 +1,5 @@ If your site is an independent project, you can create a new repository to store your site's source code. If your site is associated with an existing project, you can add the source code {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}to that project's repository, in a `/docs` folder on the default branch or on a different branch.{% else %}for your site to a `gh-pages` branch or a `docs` folder on the `master` branch in that project's repository.{% endif %} For example, if you're creating a site to publish documentation for a project that's already on {% data variables.product.product_name %}, you may want to store the source code for the site in the same repository as the project. +{% if currentVersion == "free-pro-team@latest" %}If the account that owns the repository uses {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_free_team %}, the repository must be public.{% endif %} + If you want to create a site in an existing repository, skip to the "[Creating your site](#creating-your-site)" section. diff --git a/translations/ru-RU/data/reusables/pull_requests/you-can-auto-merge.md b/translations/ru-RU/data/reusables/pull_requests/you-can-auto-merge.md index 410aec2a8e..5da386a3d1 100644 --- a/translations/ru-RU/data/reusables/pull_requests/you-can-auto-merge.md +++ b/translations/ru-RU/data/reusables/pull_requests/you-can-auto-merge.md @@ -1,3 +1,3 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} You can configure a pull request to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md index 4b0bdb1926..eed985ec8a 100644 --- a/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/ru-RU/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| Клавиша | Тип | Description | -| ---------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `действие` | `строка` | The action that was performed. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | +| Клавиша | Тип | Description | +| ---------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `действие` | `строка` | The action that was performed. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. | diff --git a/translations/ru-RU/data/variables/action_code_examples.yml b/translations/ru-RU/data/variables/action_code_examples.yml index 9aee540dac..9131d3377b 100644 --- a/translations/ru-RU/data/variables/action_code_examples.yml +++ b/translations/ru-RU/data/variables/action_code_examples.yml @@ -24,7 +24,7 @@ - labels - title: Add releases to GitHub - description: Publish Github releases in an action + description: Publish GitHub releases in an action languages: 'Dockerfile, Shell' href: elgohr/Github-Release-Action tags: @@ -32,7 +32,7 @@ - publishing - title: Publish a docker image to Dockerhub - description: A Github Action used to build and publish Docker images + description: A GitHub Action used to build and publish Docker images languages: 'Dockerfile, Shell' href: elgohr/Publish-Docker-Github-Action tags: @@ -123,7 +123,7 @@ - publishing - title: Label your Pull Requests auto-magically (using committed files) - description: Github action to label your pull requests auto-magically (using committed files) + description: GitHub action to label your pull requests auto-magically (using committed files) languages: 'TypeScript, Dockerfile, JavaScript' href: Decathlon/pull-request-labeler-action tags: @@ -132,7 +132,7 @@ - labels - title: Add Label to your Pull Requests based on the author team name - description: Github action to label your pull requests based on the author name + description: GitHub action to label your pull requests based on the author name languages: 'TypeScript, JavaScript' href: JulienKode/team-labeler-action tags: diff --git a/translations/ru-RU/data/variables/product.yml b/translations/ru-RU/data/variables/product.yml index ab42a8fb10..998ab0b171 100644 --- a/translations/ru-RU/data/variables/product.yml +++ b/translations/ru-RU/data/variables/product.yml @@ -147,10 +147,10 @@ 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://docs.github.com/rest{% elsif enterpriseServerVersions contains currentVersion %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif currentVersion == "github-ae@latest" %}https://docs.github.com/github-ae@latest/rest{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% endif %} #Use this inside command-line code blocks #Enterprise OAuth paths that don't include "/graphql" or "/api/v3" oauth_host_code: >- @@ -159,10 +159,10 @@ device_authorization_url: >- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}[`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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/graphql{% endif %} 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 89729e512c..956baf3799 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 @@ -112,7 +112,7 @@ runs: ``` 如果 `entrypoint.sh` 执行没有任何错误，则操作的状态设置为 `success`。 您还可以在操作的代码中显式设置退出代码以提供操作的状态。 更多信息请参阅“[设置操作的退出代码](/actions/creating-actions/setting-exit-codes-for-actions)”。 -1. Make your `entrypoint.sh` file executable by running the following command on your system. +1. 通过在您的系统上运行以下命令使您的 `entrypoint.sh` 文件可执行。 ```shell{:copy} $ chmod +x entrypoint.sh @@ -177,7 +177,7 @@ git push --follow-tags #### 使用公共操作的示例 -The following workflow code uses the completed _hello world_ action in the public [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action) repository. 将以下工作流程示例代码复制到 `.github/workflows/main.yml` 文件中，但将 `actions/hello-world-docker-action` 替换为您的仓库和操作名称。 您还可以将 `who-to-greet` 输入替换为您的名称。 {% if currentVersion == "free-pro-team@latest" %}Public actions can be used even if they're not published to {% data variables.product.prodname_marketplace %}. For more information, see "[Publishing an action](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)." {% endif %} +以下工作流程代码使用公共 [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action) 仓库中完整的 _hello world_ 操作。 将以下工作流程示例代码复制到 `.github/workflows/main.yml` 文件中，但将 `actions/hello-world-docker-action` 替换为您的仓库和操作名称。 您还可以将 `who-to-greet` 输入替换为您的名称。 {% if currentVersion == "free-pro-team@latest" %}公共操作即使未发布到 {% data variables.product.prodname_marketplace %} 也可使用。 更多信息请参阅“[发布操作](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)”。 {% endif %} {% raw %} **.github/workflows/main.yml** @@ -202,7 +202,7 @@ jobs: #### 使用私有操作的示例 -将以下示例工作流程代码复制到操作仓库中的 `.github/workflows/main.yml` 文件。 您还可以将 `who-to-greet` 输入替换为您的名称。 {% if currentVersion == "free-pro-team@latest" %}This private action can't be published to {% data variables.product.prodname_marketplace %}, and can only be used in this repository.{% endif %} +将以下示例工作流程代码复制到操作仓库中的 `.github/workflows/main.yml` 文件。 您还可以将 `who-to-greet` 输入替换为您的名称。 {% if currentVersion == "free-pro-team@latest" %}此操作不能发布到 {% data variables.product.prodname_marketplace %}，并且只能在此仓库中使用。{% endif %} {% raw %} **.github/workflows/main.yml** 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 012a99fb50..a271ec7ab9 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 @@ -60,7 +60,7 @@ inputs: #### `inputs.` -**必要** 要与输入关联的 `string` 识别符。 `` 的值是输入元数据的映射。 `` 必须是 `inputs` 对象中的唯一识别符。 `` 必须以字母或 `_` 开关，并且只能包含字母数字、`-` 或 `_`。 +**必要** 要与输入关联的 `string` 识别符。 `` 的值是输入元数据的映射。 `` 必须是 `inputs` 对象中的唯一识别符。 `` 必须以字母或 `_` 开头，并且只能包含字母数字、`-` 或 `_`。 #### `inputs..description` diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md index 6a1aa4d265..213e2ef2f7 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md @@ -126,7 +126,7 @@ steps: ``` {% endraw %} -This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` and `.gradle/wrapper` directories of the runner's home directory. The cache key will be the hashed contents of the gradle build files (including the Gradle wrapper properties file), so any changes to them will invalidate the cache. +此工作流程将保存本地 Gradle 包缓存的内容，位于运行器主目录的 `.gradle/caches` 和 `.gradle/wrapper` 目录中。 缓存键将是 gradle 构建文件（包括 Gradle wrapper 属性文件）的哈希内容，因此对它们的任何更改都将使缓存无效。 ### 将工作流数据打包为构件 diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-net.md b/translations/zh-CN/content/actions/guides/building-and-testing-net.md index 0920b18bcf..b4cf80a011 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-net.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-net.md @@ -90,7 +90,7 @@ jobs: #### Using a specific .NET version -You can configure your job to use a specific version of .NET, such as `3.1.3`. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of .NET 3. +You can configure your job to use a specific version of .NET, such as `3.1.3`. 或者，您也可以使用语义版本语法来获得最新的次要版本。 This example uses the latest minor release of .NET 3. {% raw %} ```yaml diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md index bf4620724a..5894fdb11f 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md @@ -76,7 +76,7 @@ jobs: `setup-node` 操作采用 Node.js 版本作为输入，并在运行器上配置该版本。 `setup-node` 操作从每个运行器上的工具缓存中查找特定版本的 Node.js，并将必要的二进制文件添加到 `PATH`，这可继续用于作业的其余部分。 使用 `setup-node` 操作是 Node.js 与 {% data variables.product.prodname_actions %} 结合使用时的推荐方式，因为它能确保不同运行器和不同版本的 Node.js 行为一致。 如果使用自托管运行器，则必须安装 Node.js 并将其添加到 `PATH`。 -The template includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. "x" 是一个通配符，与版本的最新次要版本和修补程序版本匹配。 `node-version` 阵列中指定的每个 Node.js 版本都会创建一个运行相同步骤的作业。 +模板包含一个矩阵策略：用四个 Node.js 版本 10.x、12.x、14.x 和 15.x 构建和测试代码， "x" 是一个通配符，与版本的最新次要版本和修补程序版本匹配。 `node-version` 阵列中指定的每个 Node.js 版本都会创建一个运行相同步骤的作业。 每个作业都可以使用 `matrix` 上下文访问矩阵 `node-version` 阵列中定义的值。 `setup-node` 操作使用上下文作为 `node-version` 输入。 `setup-node` 操作在构建和测试代码之前使用不同的 Node.js 版本配置每个作业。 有关矩阵策略和上下文的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)”和“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。 diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-python.md b/translations/zh-CN/content/actions/guides/building-and-testing-python.md index 8c8e0bac7f..7de41ae68f 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-python.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-python.md @@ -136,7 +136,7 @@ jobs: #### 使用特定的 Python 版本 -您可以配置 python 的特定版本。 例如，3.8。 Alternatively, you can use semantic version syntax to get the latest minor release. 此示例使用 Python 3 最新的次要版本。 +您可以配置 python 的特定版本。 例如，3.8。 或者，您也可以使用语义版本语法来获得最新的次要版本。 此示例使用 Python 3 最新的次要版本。 {% raw %} diff --git a/translations/zh-CN/content/actions/guides/publishing-docker-images.md b/translations/zh-CN/content/actions/guides/publishing-docker-images.md index e37eaec9fd..ef99ce45a0 100644 --- a/translations/zh-CN/content/actions/guides/publishing-docker-images.md +++ b/translations/zh-CN/content/actions/guides/publishing-docker-images.md @@ -10,7 +10,7 @@ versions: type: tutorial topics: - 打包 - - Publishing + - 发布 - Docker --- diff --git a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md index 9905cf3a8d..6cd7c893eb 100644 --- a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md +++ b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-gradle.md @@ -10,7 +10,7 @@ versions: type: tutorial topics: - 打包 - - Publishing + - 发布 - Java - Gradle --- diff --git a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md index f35b52091a..91a7036c87 100644 --- a/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md +++ b/translations/zh-CN/content/actions/guides/publishing-java-packages-with-maven.md @@ -10,7 +10,7 @@ versions: type: tutorial topics: - 打包 - - Publishing + - 发布 - Java - Maven --- diff --git a/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md b/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md index 255bb3493c..2de9a90647 100644 --- a/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md @@ -11,7 +11,7 @@ versions: type: tutorial topics: - 打包 - - Publishing + - 发布 - Node - JavaScript --- @@ -93,11 +93,11 @@ always-auth=true 每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件发生时运行。 如果 CI 测试通过，工作流程会将包发布到 {% data variables.product.prodname_registry %}。 -#### Configuring the destination repository +#### 配置目标仓库 -If you don't provide the `repository` key in your *package.json* file, then {% 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, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. +如果您没有在 *package.json* 文件中提供 `repository` 键，则 {% data variables.product.prodname_registry %} 将包发布到您在 *package.json* 文件的 `name` 字段中指定的 {% data variables.product.prodname_dotcom %} 仓库。 例如，名为 `@my-org/test` 的包将被发布到 `my-org/test` {% data variables.product.prodname_dotcom %} 仓库。 -However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository. +但是，如果您提供了 `repository` 键，则该键中的仓库将被用作 {% data variables.product.prodname_registry %} 的目标 npm 注册表。 例如，发布以下 *package.json* 将导致名为 `my-amazing-package` 的包被发布到 `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} 仓库。 ```json { @@ -108,11 +108,11 @@ However, if you do provide the `repository` key, then the repository in that key }, ``` -#### Authenticating to the destination repository +#### 向目标仓库验证 -To authenticate to the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN` from your repository. It is created automatically and has _read_ and _write_ permissions for packages in the repository where the workflow runs. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)." +要向工作流程中的 {% data variables.product.prodname_registry %} 注册表进行验证，您可以使用仓库的 `GITHUB_TOKEN`。 它是自动创建的，对工作流程运行所在仓库中的包具有_读取_和_写入_权限。 更多信息请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow)。 -If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." +如果要将包发布到其他仓库，您必须使用对目标仓库中的包具有写入权限的个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”和“[加密密码](/actions/reference/encrypted-secrets)”。 #### 示例工作流程 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 2304c7813c..ffdf91334f 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 @@ -63,7 +63,7 @@ type: 'overview' {% data reusables.github-actions.usage-api-requests %} - **作业矩阵** - {% data reusables.github-actions.usage-matrix-limits %} -### 自托管运行器支持的操作系统 +### Supported architectures and operating systems for self-hosted runners 自托管运行器应用程序支持以下操作系统。 @@ -92,6 +92,14 @@ type: 'overview' - macOS 10.13 (High Sierra) 或更高版本 +#### Architectures + +The following processor architectures are supported for the self-hosted runner application. + +- `x64` - Linux, macOS, Windows. +- `ARM64` - Linux only. +- `ARM32` - Linux only. + {% if enterpriseServerVersions contains currentVersion %} ### 自托管运行器与 {% data variables.product.prodname_dotcom %} 之间的通信 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 0ce4af807a..5dbb159d4e 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 @@ -29,7 +29,7 @@ type: tutorial * `self-hosted`：应用到所有自托管运行器的默认标签。 * `linux`、`windows` 或 `macOS`：根据操作系统应用。 -* `x86`、`x64`、`ARM` 或 `ARM64`：根据硬件架构应用。 +* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. 您可以使用您工作流程的 YAML 将作业发送到这些标签的组合。 在此示例中，与所有三个标签匹配的自托管运行器将有资格运行该作业： @@ -64,11 +64,11 @@ runs-on: [self-hosted, linux, x64, gpu] ### 自托管运行器的路由优先级 -When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels: +将作业路由到自托管运行器时，{% data variables.product.prodname_dotcom %} 将查找与作业的 `runs-on` 标签匹配的运行器： -1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level{% if currentVersion ver_gt "enterprise-server@2.21" %}, then at the enterprise level{% endif %}. -2. The job is then sent to the first matching runner that is online and idle. - - If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners. - - If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners. - - If there are no matching runners at any level, the job will fail. - - If the job remains queued for more than 24 hours, the job will fail. +1. {% data variables.product.prodname_dotcom %} 先在仓库级别搜索运行器，然后在组织级别搜索运行器{% if currentVersion ver_gt "enterprise-server@2.21" %}，然后在企业级别搜索运行器{% endif %}。 +2. 然后，将作业发送到第一个联机且空闲的匹配运行器。 + - 如果所有匹配的联机运行器都处于忙碌状态，则作业将在匹配联机运行器数量最多的级别排队。 + - 如果所有匹配的运行器都处于脱机状态，则作业将在匹配脱机运行器数量最多的级别排队。 + - 如果在任何级别都没有匹配的运行器，则作业将失败。 + - 如果作业排队的时间超过 24 小时，则作业将失败。 diff --git a/translations/zh-CN/content/actions/index.md b/translations/zh-CN/content/actions/index.md index 578fdacadf..5746e429bd 100644 --- a/translations/zh-CN/content/actions/index.md +++ b/translations/zh-CN/content/actions/index.md @@ -23,7 +23,7 @@ featuredLinks: - /actions/reference/encrypted-secrets changelog: - - title: Environments, environment protection rules and environment secrets (beta) + title: 环境、环境保护规则和环境密码（测试版） date: '2020-12-15' href: https://github.blog/changelog/2020-12-15-github-actions-environments-environment-protection-rules-and-environment-secrets-beta/ - 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 bbc2eead71..3629e069d6 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 @@ -70,7 +70,7 @@ steps: #### 使用 SHA -如果需要更可靠的版本控制，应使用与操作版本关联的 SHA 值。 SHA 是不可变的，因此比标记或分支更可靠。 但是，此方法意味着您不会自动接收操作的更新，包括重要的 Bug 修复和安全更新。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}You must use a commit's full SHA value, and not an abbreviated value. {% endif %}This example targets an action's SHA: +如果需要更可靠的版本控制，应使用与操作版本关联的 SHA 值。 SHA 是不可变的，因此比标记或分支更可靠。 但是，此方法意味着您不会自动接收操作的更新，包括重要的 Bug 修复和安全更新。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}您必须使用提交的完整 SHA 值，而不是缩写值。 {% endif %}此示例针对操作的 SHA： ```yaml steps: @@ -79,7 +79,7 @@ steps: #### 使用分支 -Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. 此示例针对名为 `@main`的分支： +为操作指定目标分支意味着它将始终在该分支上运行当前的版本。 如果对分支的更新包含重大更改，此方法可能会造成问题。 此示例针对名为 `@main`的分支： ```yaml steps: diff --git a/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md index 83461cc14f..deb455671a 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/introduction-to-github-actions.md @@ -149,7 +149,7 @@ _操作_ 是独立命令，它们组合到_步骤_以创建_作业_。 操作是 ``` - 将 check-bats-version 作业中运行的所有步骤组合在一起。 Each item nested under this section is a separate action or shell command. + 将 check-bats-version 作业中运行的所有步骤组合在一起。 此部分下嵌套的每项都是一个单独的操作或 shell 命令。 diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index dc16f928e8..fdb496107e 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -9,7 +9,7 @@ versions: type: tutorial topics: - CircleCI - - Migration + - 迁移 - CI - CD --- diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 3eb7b38c32..f1e9ff8013 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -7,7 +7,7 @@ versions: type: tutorial topics: - GitLab - - Migration + - 迁移 - CI - CD --- diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md index 43e73f1102..cac22098a9 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md @@ -9,7 +9,7 @@ versions: type: tutorial topics: - Jenkins - - Migration + - 迁移 - CI - CD --- diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index 4e7434b3e3..dd09d1fdbc 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -9,7 +9,7 @@ versions: type: tutorial topics: - Travis CI - - Migration + - 迁移 - CI - CD --- diff --git a/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md index c2d283ad54..c259cbf40a 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/security-hardening-for-github-actions.md @@ -117,7 +117,7 @@ topics: 例如，您可以使用审核日志跟踪 `action:org.update_actions_secret` 事件，以跟踪组织机密的更改： ![审核日志条目](/assets/images/help/repository/audit-log-entries.png) -以下表格描述了您可以在审核日志中找到的 {% data variables.product.prodname_actions %} 事件。 For more information on using the audit log, see "[Reviewing the audit log for your organization](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." +以下表格描述了您可以在审核日志中找到的 {% data variables.product.prodname_actions %} 事件。 有关使用审核日志的更多信息，请参阅“[查看组织的审核日志](/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)”。 #### 机密管理的事件 | 操作 | 描述 | diff --git a/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md b/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md index 3f67ba6102..7e7eed3ce3 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md +++ b/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-with-your-organization.md @@ -76,7 +76,7 @@ type: 'how_to' ![工作流程模板文件](/assets/images/help/images/workflow-template-files.png) -### Using a workflow template from your organization +### 使用组织的工作流程模板 此程序展示组织成员如何查找并使用工作流程模板来创建新的工作流程。 只要是组织成员，都可以使用组织的工作流程模板。 diff --git a/translations/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md index 2f913e932d..a2636a38fe 100644 --- a/translations/zh-CN/content/actions/quickstart.md +++ b/translations/zh-CN/content/actions/quickstart.md @@ -69,7 +69,7 @@ topics: {% endif %} {% data reusables.repositories.view-failed-job-results-superlinter %} -### More workflow templates +### 更多工作流程模板 {% data reusables.actions.workflow-template-overview %} @@ -123,7 +123,7 @@ topics: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. In the left sidebar, click the workflow you want to run. +1. 在左侧边栏中，单击您想要运行的工作流程。 ![选择 say hello 作业](/assets/images/help/repository/say-hello-job.png) 1. 在右侧，单击 **Run workflow（运行工作流程）**下拉菜单，然后单击 **Run workflow（运行工作流程）**。 （可选）您可以在运行工作流程之前在“问候的人（Person to greet）”输入中输入自定义消息。 ![触发手动工作流程](/assets/images/help/repository/manual-workflow-trigger.png) diff --git a/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md b/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md index a053b8e35c..3620a90dbf 100644 --- a/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md +++ b/translations/zh-CN/content/actions/reference/authentication-in-a-workflow.md @@ -79,18 +79,18 @@ versions: 有关 {% data variables.product.prodname_github_apps %} 可通过各种权限访问的 API 端点的信息，请参阅“[{% data variables.product.prodname_github_app %} 权限](/rest/reference/permissions-required-for-github-apps)”。 -| 权限 | 访问类型 | 通过复刻的仓库访问 | -| -------- | ---- | --------- | -| 操作 | 读/写 | 读取 | -| 检查 | 读/写 | 读取 | -| 内容 | 读/写 | 读取 | -| 部署 | 读/写 | 读取 | -| issues | 读/写 | 读取 | -| 元数据 | 读取 | 读取 | -| 包 | 读/写 | 读取 | -| 拉取请求 | 读/写 | 读取 | -| 仓库项目 | 读/写 | 读取 | -| statuses | 读/写 | 读取 | +| 权限 | 访问类型 | 通过复刻的仓库访问 | +| ---- | ---- | --------- | +| 操作 | 读/写 | 读取 | +| 检查 | 读/写 | 读取 | +| 内容 | 读/写 | 读取 | +| 部署 | 读/写 | 读取 | +| 议题 | 读/写 | 读取 | +| 元数据 | 读取 | 读取 | +| 包 | 读/写 | 读取 | +| 拉取请求 | 读/写 | 读取 | +| 仓库项目 | 读/写 | 读取 | +| 状态 | 读/写 | 读取 | 如果您需要的令牌需要 `GITHUB_TOKEN` 中未提供的权限，您可以创建个人访问令牌并将其设置为仓库中的密码： diff --git a/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 96fa339d1b..f53534c43d 100644 --- a/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,7 +75,7 @@ env: - 以 `a-Z` 或 `_` 开头。 - 后跟 `a-Z` `0-9` `-` 或 `_`。 -#### Determining when to use contexts +#### 确定何时使用上下文 {% data reusables.github-actions.using-context-or-environment-variables %} @@ -111,7 +111,7 @@ env: `env` 上下文包含已在工作流程、作业或步骤中设置的环境变量。 有关在工作流程中设置环境变量的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)”。 -`env` 上下文语法允许您在工作流程文件中使用环境变量的值。 You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. 有关步骤语法的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)”。 +`env` 上下文语法允许您在工作流程文件中使用环境变量的值。 您可以在**步骤**的任何键值中使用 `env` 上下文，但 `id` 和 `uses` 键除外。 有关步骤语法的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)”。 如果您想要在运行器中使用环境变量的值，请使用运行器操作系统的正常方法来读取环境变量。 @@ -362,9 +362,9 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat') `fromJSON(value)` -Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string. +返回 `value` 的 JSON 对象或 JSON 数据类型。 您可以使用此函数来提供 JSON 对象作为评估表达式或从字符串转换环境变量。 -##### Example returning a JSON object +##### 返回 JSON 对象的示例 此工作流程在一个作业中设置 JSON矩阵，并使用输出和 `fromJSON` 将其传递到下一个作业。 @@ -390,9 +390,9 @@ jobs: ``` {% endraw %} -##### Example returning a JSON data type +##### 返回 JSON 数据类型的示例 -This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer. +此工作流程使用 `fromJSON` 将环境变量从字符串转换为布尔值或整数。 {% raw %} ```yaml diff --git a/translations/zh-CN/content/actions/reference/environment-variables.md b/translations/zh-CN/content/actions/reference/environment-variables.md index 7441e43781..35474db699 100644 --- a/translations/zh-CN/content/actions/reference/environment-variables.md +++ b/translations/zh-CN/content/actions/reference/environment-variables.md @@ -36,9 +36,9 @@ jobs: Last_Name: Octocat ``` -To use the value of an environment variable in a workflow file, you should use the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). If you want to use the value of an environment variable inside a runner, you can use the runner operating system's normal method for reading environment variables. +要在工作流程文件中使用环境变量的值，您应该使用 [`env` 上下文](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)。 如果要在运行器中使用环境变量的值，您可以使用运行器操作系统的正常方法来读取环境变量。 -If you use the workflow file's `run` key to read environment variables from within the runner operating system (as shown in the example above), the variable is substituted in the runner operating system after the job is sent to the runner. For other parts of a workflow file, you must use the `env` context to read environment variables; this is because workflow keys (such as `if`) require the variable to be substituted during workflow processing before it is sent to the runner. +如果使用工作流程文件的 `run` 键从运行器操作系统中读取环境变量（如上例所示），则在作业发送到运行器后，该变量将在运行器操作系统中被替换。 对于工作流程文件的其他部分，必须使用 `env` 上下文来读取环境变量；这是因为工作流程键（例如 `if`）需要在发送到运行器之前，在工作流程处理过程中替换变量。 您也可以使用 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`GITHUB_ENV` environment file{% else %} `set-env` 工作流程命令{% endif %} 设置工作流程中的以下步骤可以使用的环境变量。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}环境文件{% else %} `set-env` 命令{% endif %}可直接由操作使用，或使用 `run` 关键字作为工作流程文件中的 shell 命令。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)”。 @@ -69,11 +69,11 @@ If you use the workflow file's `run` key to read environment variables from with {% tip %} -**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` +**注：**如果需要在作业中使用工作流程运行的 URL，您可以组合这些环境变量：`$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID` {% endtip %} -#### Determining when to use default environment variables or contexts +#### 确定何时使用默认环境变量或上下文 {% data reusables.github-actions.using-context-or-environment-variables %} diff --git a/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md index b2d0f7424c..d5a3e7c259 100644 --- a/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md @@ -80,7 +80,7 @@ versions: 您可以使用 [crontab guru](https://crontab.guru/) 帮助生成计划任务语法并确认它在何时运行。 为帮助您开始，我们还提供了一系列 [crontab guru 示例](https://crontab.guru/examples.html)。 -Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, please see "[Notifications for workflow runs](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)." +计划工作流程的通知将发送给最后修改工作流程文件中的 cron 语法的用户。 更多信息请参阅“[工作流程运行通知](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)”。 ### 手动事件 @@ -354,15 +354,15 @@ jobs: ``` {% endraw %} -#### `issues` +#### `议题` 在发生 `issues` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[议题](/rest/reference/issues)”。 {% data reusables.github-actions.branch-requirement %} -| Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------ | -| [`issues`](/webhooks/event-payloads/#issues) | - `opened`
- `edited`
- `deleted`
- `transferred`
- `pinned`
- `unpinned`
- `closed`
- `reopened`
- `assigned`
- `unassigned`
- `labeled`
- `unlabeled`
- `locked`
- `unlocked`
- `milestoned`
- `demilestoned` | 默认分支上的最新提交 | 默认分支 | +| Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | +| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------ | +| [`议题`](/webhooks/event-payloads/#issues) | - `opened`
- `edited`
- `deleted`
- `transferred`
- `pinned`
- `unpinned`
- `closed`
- `reopened`
- `assigned`
- `unassigned`
- `labeled`
- `unlabeled`
- `locked`
- `unlocked`
- `milestoned`
- `demilestoned` | 默认分支上的最新提交 | 默认分支 | {% data reusables.developer-site.limit_workflow_to_activity_types %} diff --git a/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md index bf8e5733ba..b242a6f31f 100644 --- a/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md @@ -41,12 +41,17 @@ Windows 虚拟机配置为以禁用了用户帐户控制 (UAC) 的管理员身 ### 支持的运行器和硬件资源 -每台虚拟机都有相同的硬件资源。 +Hardware specification for Windows and Linux virtual machines: - 2 核 CPU - 7 GB RAM 内存 - 14 GB SSD 硬盘空间 +Hardware specification for macOS virtual machines: +- 3 核 CPU +- 14 GB RAM 内存 +- 14 GB SSD 硬盘空间 + {% data reusables.github-actions.supported-github-runners %} {% data reusables.github-actions.ubuntu-runner-preview %} @@ -71,9 +76,13 @@ Windows 虚拟机配置为以禁用了用户帐户控制 (UAC) 的管理员身 {% data variables.product.prodname_dotcom %} 托管的运行器除了上述参考中列出的包之外，还包括操作系统的默认内置工具。 例如，Ubuntu 和 macOS 运行器除了其他默认工具之外，还包括 `grep`、`find` 和 `which`。 -工作流程日志包括指向运行器上预安装的工具的链接。 更多信息请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。 +Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will tell you the the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -如果有您想要请求的工具，请在 [actions/virtual-environments](https://github.com/actions/virtual-environments) 打开一个议题。 +We recommend using actions to interact with the software installed on runners. This approach has several benefits: +- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters +- It ensures the tool versions used in your workflow will remain the same regardless of software updates + +如果有您想要请求的工具，请在 [actions/virtual-environments](https://github.com/actions/virtual-environments) 打开一个议题。 This repository also contains announcements about all major software updates on runners. ### IP 地址 @@ -83,11 +92,11 @@ Windows 虚拟机配置为以禁用了用户帐户控制 (UAC) 的管理员身 {% endnote %} -Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP address ranges as the Azure datacenters. macOS runners are hosted in {% data variables.product.prodname_dotcom %}'s own macOS cloud. +Windows 和 Ubuntu 运行程序托管在 Azure 中，随后具有与 Azure 数据中心相同的 IP 地址范围。 macOS 运行器托管在 {% data variables.product.prodname_dotcom %} 自己的 macOS 云中。 -To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API . For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint. You can use this list of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources. +要获取 {% data variables.product.prodname_actions %} 用于 {% data variables.product.prodname_dotcom %} 托管运行器的 IP 地址范围列表，您可以使用 {% data variables.product.prodname_dotcom %} REST API。 更多信息请参阅“[获取 GitHub 元信息](/rest/reference/meta#get-github-meta-information)”端点响应中的 `actions` 键。 如果需要一个允许列表来阻止未经授权访问您的内部资源，您可以使用此 IP 地址列表。 -The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. +API 返回的 {% data variables.product.prodname_actions %} IP 地址列表每周更新一次。 ### 文件系统 diff --git a/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md b/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md index 8a03e7f70c..85c9112587 100644 --- a/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md +++ b/translations/zh-CN/content/actions/reference/workflow-commands-for-github-actions.md @@ -313,11 +313,11 @@ 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. +为系统 `PATH` 变量预先设置一个目录，使其可用于当前作业中的所有后续操作；当前运行的操作无法访问更新的路径变量。 要查看作业的当前定义路径，您可以在步骤或操作中使用 `echo "$PATH"`。 #### 示例 -This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`: +此示例演示如何将用户 `$HOME/.local/bin` 目录添加到 `PATH`： ``` bash echo "$HOME/.local/bin" >> $GITHUB_PATH diff --git a/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md index afd0397037..9e173ed6c4 100644 --- a/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md @@ -27,7 +27,7 @@ versions: ### `on` -**必填**。 The name of the {% data variables.product.prodname_dotcom %} event that triggers the workflow. 您可以提供单一事件 `string`、事件的 `array`、事件 `types` 的 `array` 或事件配置 `map`，以安排工作流程的运行，或将工作流程的执行限于特定文件、标记或分支更改。 有关可用事件的列表，请参阅“[触发工作流程的事件](/articles/events-that-trigger-workflows)”。 +**必填**。 触发工作流程的 {% data variables.product.prodname_dotcom %} 事件的名称。 您可以提供单一事件 `string`、事件的 `array`、事件 `types` 的 `array` 或事件配置 `map`，以安排工作流程的运行，或将工作流程的执行限于特定文件、标记或分支更改。 有关可用事件的列表，请参阅“[触发工作流程的事件](/articles/events-that-trigger-workflows)”。 {% data reusables.github-actions.actions-on-examples %} @@ -187,7 +187,7 @@ on: ### `env` -A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. 更多信息请参阅 [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv)。 +环境变量的 `map` 可用于工作流程中所有作业的步骤。 您还可以设置仅适用于单个作业的步骤或单个步骤的环境变量。 更多信息请参阅 [`jobs..env`](#jobsjob_idenv) and [`jobs..steps[*].env`](#jobsjob_idstepsenv)。 {% data reusables.repositories.actions-env-var-note %} @@ -286,7 +286,7 @@ jobs: ### `jobs..runs-on` -**必填**。 The type of machine to run the job on. 机器可以是 {% data variables.product.prodname_dotcom %} 托管的运行器或自托管的运行器。 +**必填**。 要运行作业的机器类型。 机器可以是 {% data variables.product.prodname_dotcom %} 托管的运行器或自托管的运行器。 {% data reusables.actions.enterprise-github-hosted-runners %} @@ -640,15 +640,15 @@ jobs: 您可以使用 `shell` 关键词覆盖运行器操作系统中默认的 shell 设置。 您可以使用内置的 `shell` 关键词，也可以自定义 shell 选项集。 -| 支持的平台 | `shell` 参数 | 描述 | 内部运行命令 | -| ------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | -| 所有 | `bash` | 非 Windows 平台上回退到 `sh` 的默认 shell。 指定 Windows 上的 bash shell 时，将使用 Git for Windows 随附的 bash shel。 | `bash --noprofile --norc -eo pipefail {0}` | -| 所有 | `pwsh` | PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `pwsh -command ". '{0}'"` | -| 所有 | `python` | 执行 python 命令。 | `python {0}` | -| Linux / macOS | `sh` | 未提供 shell 且 在路径中找不到 `bash` 时的非 Windows 平台的后退行为。 | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %} 将扩展名 `.cmd` 附加到您的脚本名称并替换 `{0}`。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `pwsh` | 这是 Windows 上使用的默认 shell。 PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead. | `pwsh -command ". '{0}'"`. | -| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `powershell -command ". '{0}'"`. | +| 支持的平台 | `shell` 参数 | 描述 | 内部运行命令 | +| ------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | +| 所有 | `bash` | 非 Windows 平台上回退到 `sh` 的默认 shell。 指定 Windows 上的 bash shell 时，将使用 Git for Windows 随附的 bash shel。 | `bash --noprofile --norc -eo pipefail {0}` | +| 所有 | `pwsh` | PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `pwsh -command ". '{0}'"` | +| 所有 | `python` | 执行 python 命令。 | `python {0}` | +| Linux / macOS | `sh` | 未提供 shell 且 在路径中找不到 `bash` 时的非 Windows 平台的后退行为。 | `sh -e {0}` | +| Windows | `cmd` | {% data variables.product.prodname_dotcom %} 将扩展名 `.cmd` 附加到您的脚本名称并替换 `{0}`。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | +| Windows | `pwsh` | 这是 Windows 上使用的默认 shell。 PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 如果自托管的 Windows 运行器没有安装 _PowerShell Core_，则使用 _PowerShell Desktop_ 代替。 | `pwsh -command ". '{0}'"`. | +| Windows | `powershell` | PowerShell 桌面。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `powershell -command ". '{0}'"`. | #### 使用 bash 运行脚本的示例 @@ -677,7 +677,7 @@ steps: shell: pwsh ``` -#### Example: Using PowerShell Desktop to run a script +#### 示例：使用 PowerShell 桌面运行脚本 ```yaml steps: @@ -711,14 +711,14 @@ steps: shell: perl {0} ``` -The command used, `perl` in this example, must be installed on the runner. For information about the software included on GitHub-hosted runners, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)." +此示例中使用的命令 `perl` 必须安装在运行器上。 有关 GitHub 托管运行器中所包含软件的信息，请参阅“[GitHub 托管运行器的规格](/actions/reference/specifications-for-github-hosted-runners#supported-software)”。 #### 退出代码和错误操作首选项 至于内置的 shell 关键词，我们提供由 {% data variables.product.prodname_dotcom %} 托管运行程序执行的以下默认值。 在运行 shell 脚本时，您应该使用这些指南。 - `bash`/`sh`： - - Fail-fast behavior using `set -eo pipefail`: Default for `bash` and built-in `shell`. 它还是未在非 Windows 平台上提供选项时的默认值。 + - 使用 `set -eo pipefail` 的快速失败行为：`bash` 和内置 `shell` 的默认值。 它还是未在非 Windows 平台上提供选项时的默认值。 - 您可以向 shell 选项提供模板字符串，以退出快速失败并接管全面控制权。 例如 `bash {0}`。 - sh 类 shell 使用脚本中最后执行的命令的退出代码退出，也是操作的默认行为。 运行程序将根据此退出代码将步骤的状态报告为失败/成功。 @@ -1172,7 +1172,7 @@ volumes: - `**`： 匹配零个或多个任何字符。 - `?`：匹配零个或一个字符。 例如 `Octoc?t` 匹配 `Octocat`。 - `+`: 匹配一个或多个前置字符。 -- `[]` 匹配列在括号中或包含在范围内的一个字符。 范围只能包含 `a-z`、`A-Z` 和 `0-9`。 For example, the range`[0-9a-z]` matches any digit or lowercase letter. 例如，`[CB]at` 匹配 `Cat` 或 `Bat`，`[1-2]00` 匹配 `100` 和 `200`。 +- `[]` 匹配列在括号中或包含在范围内的一个字符。 范围只能包含 `a-z`、`A-Z` 和 `0-9`。 例如，范围 `[0-9a-z]` 匹配任何数字或小写字母。 例如，`[CB]at` 匹配 `Cat` 或 `Bat`，`[1-2]00` 匹配 `100` 和 `200`。 - `!`：在模式开始时，它将否定以前的正模式。 如果不是第一个字符，它就没有特殊的意义。 字符 `*`、`[` 和 `!` 是 YAML 中的特殊字符。 如果模式以 `*`、`[` 或 `!` 开头，必须用引号括住模式。 @@ -1190,16 +1190,16 @@ volumes: #### 匹配分支和标记的模式 -| 模式 | 描述 | 示例匹配 | -| ------------------------------------------------------ | --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | -| `功能/*` | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 | `feature/my-branch`

`feature/your-branch` | -| `功能/**` | `**` 通配符匹配任何字符，包括分支和标记名称中的斜杠 (`/`)。 | `feature/beta-a/my-branch`

`feature/your-branch`

`feature/mona/the/octocat` | -| `main`

`releases/mona-the-octcat` | 匹配分支或标记名称的确切名称。 | `main`

`releases/mona-the-octocat` | -| `'*'` | 匹配所有不包含斜杠 (`/`) 的分支和标记名称。 `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `main`

`releases` | -| `'**'` | 匹配所有分支和标记名称。 这是不使用 `branches` or `tags` 过滤器时的默认行为。 | `all/the/branches`

`every/tag` | -| `'*功能'` | `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `mona-feature`

`feature`

`ver-10-feature` | -| `v2*` | 匹配以 `v2` 开头的分支和标记名称。 | `v2`

`v2.0`

`v2.9` | -| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2 | `v1.10.1`

`v2.0.0` | +| 模式 | 描述 | 示例匹配 | +| ------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| `功能/*` | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 | `feature/my-branch`

`feature/your-branch` | +| `功能/**` | `**` 通配符匹配任何字符，包括分支和标记名称中的斜杠 (`/`)。 | `feature/beta-a/my-branch`

`feature/your-branch`

`feature/mona/the/octocat` | +| `main`

`releases/mona-the-octcat` | 匹配分支或标记名称的确切名称。 | `main`

`releases/mona-the-octocat` | +| `'*'` | 匹配所有不包含斜杠 (`/`) 的分支和标记名称。 `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `main`

`releases` | +| `'**'` | 匹配所有分支和标记名称。 这是不使用 `branches` or `tags` 过滤器时的默认行为。 | `all/the/branches`

`every/tag` | +| `'*功能'` | `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `mona-feature`

`feature`

`ver-10-feature` | +| `v2*` | 匹配以 `v2` 开头的分支和标记名称。 | `v2`

`v2.0`

`v2.9` | +| `v[12].[0-9]+.[0-9]+` | 将所有语义版本控制分支和标记与主要版本 1 或 2 匹配 | `v1.10.1`

`v2.0.0` | #### 匹配文件路径的模式 diff --git a/translations/zh-CN/content/admin/configuration/configuring-code-scanning-for-your-appliance.md b/translations/zh-CN/content/admin/configuration/configuring-code-scanning-for-your-appliance.md index cc2f9fc931..09c06eeb90 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-code-scanning-for-your-appliance.md +++ b/translations/zh-CN/content/admin/configuration/configuring-code-scanning-for-your-appliance.md @@ -73,7 +73,7 @@ If the server on which you are running {% endif %} #### Enabling code scanning for individual repositories -After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. 默认 {% data variables.product.prodname_code_scanning %} 工作流程使用 `on.push` 事件触发代码扫描 - 每次推送到任何包含工作流程文件的分支时触发。 +After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." ### 使用 {% data variables.product.prodname_codeql_runner %} 运行 {% data variables.product.prodname_code_scanning %} 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 %}. diff --git a/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md index fe85162e3e..8b71a1827a 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/configuring-data-encryption-for-your-enterprise.md @@ -20,7 +20,7 @@ versions: 您提供的钥匙存储在 {% data variables.product.company_short %} 管理的密钥保管库的硬件安全模块 (HSM) 中。 -要配置加密密钥，请使用 REST API。 有许多 API 端点，例如检查加密状态、更新加密密钥以及删除加密密钥的端点。 请注意，删除密钥将冻结企业。 有关 API 端点的详细信息，请参阅 REST API 文档中的“[休息时加密](/rest/reference/enterprise-admin#encryption-at-rest)”。 +要配置加密密钥，请使用 REST API。 There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. 有关 API 端点的详细信息，请参阅 REST API 文档中的“[休息时加密](/rest/reference/enterprise-admin#encryption-at-rest)”。 ### 添加或更新加密密钥 @@ -48,24 +48,24 @@ versions: curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` -### 删除加密密钥 +### Disabling your encryption key -要冻结企业（例如在发生违规的情况下），可以通过删除加密密钥来禁用休息时加密。 +To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled. -要在删除加密密钥后解冻企业，请联系支持人员。 更多信息请参阅“[关于 {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)”。 - -1. 要删除密钥并禁用休息时加密，请使用 `DELETE /enterprise/encryption` 端点。 +1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently. ```shell curl -X DELETE http(s)://hostname/api/v3/enterprise/encryption ``` -2. （可选）检查删除操作的状态。 +2. （可选）检查删除操作的状态。 It takes approximately ten minutes to disable encryption at rest. ```shell curl -X GET http(s)://hostname/api/v3/enterprise/encryption/status/request_id ``` +To unfreeze your enterprise after you've disabled your encryption key, contact support. 更多信息请参阅“[关于 {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)”。 + ### 延伸阅读 - REST API 文档中的“[休息时加密](/rest/reference/enterprise-admin#encryption-at-rest)” diff --git a/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md b/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md index cb06da9992..2a7a6480b2 100644 --- a/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md +++ b/translations/zh-CN/content/admin/enterprise-management/upgrading-github-enterprise-server.md @@ -29,6 +29,26 @@ versions: {% endnote %} +{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %} + +### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later + +Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table. + +| 用户许可 | vCPU | 内存 | 附加的存储容量 | 根存储容量 | +|:----------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------:| +| 试用版、演示版或 10 个轻度用户 | **4**
_Up from 2_ | **32 GB**
_Up from 16 GB_ | **150 GB**
_Up from 100 GB_ | 200 GB | +| 10-3000 | **8**
_Up from 4_ | **48 GB**
_Up from 32 GB_ | **300 GB**
_Up from 250 GB_ | 200 GB | +| 3000-5000 | **12**
_Up from 8_ | 64 GB | 500 GB | 200 GB | +| 5000-8000 | **16**
_Up from 12_ | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | **20**
_Up from 16_ | **160 GB**
_Up from 128 GB_ | 1000 GB | 200 GB | + +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% endif %} + ### 生成快照 快照是虚拟机 (VM) 在某一时间点的检查点。 强烈建议在升级虚拟机之前生成快照，这样一来，如果升级失败，您可以将 VM 还原到快照状态。 如果您要升级到新的功能版本，则必须生成 VM 快照。 如果您要升级到补丁版本，可以连接现有数据磁盘。 diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md index a284dbad9e..098ff48a13 100644 --- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md @@ -9,13 +9,7 @@ versions: enterprise-server: '>=2.22' --- -{% if currentVersion == "enterprise-server@2.22" %} -{% note %} - -**注：**{% data variables.product.prodname_ghe_server %} 2.22 上的 {% data variables.product.prodname_actions %} 支持是有限的公测版。 查看下面的外部存储要求并[注册测试版](https://resources.github.com/beta-signup/)。 - -{% endnote %} -{% endif %} +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} @@ -23,11 +17,33 @@ versions: This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies. +{% endif %} + ### Review hardware considerations +{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %} + +{% note %} + +**Note**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)。” + +{% endnote %} + +{% endif %} + {% data reusables.actions.enterprise-hardware-considerations %} -{% endif %} +For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform. + +- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations) +- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations) +- [Google Cloud 平台](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) +- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) +- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) +- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations) +- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations) + +{% data reusables.enterprise_installation.about-adjusting-resources %} ### External storage requirements @@ -55,7 +71,7 @@ This article explains how site administrators can configure {% data variables.pr ### 启用 {% data variables.product.prodname_actions %} -{% data variables.product.prodname_ghe_server %} 2.22 上的 {% data variables.product.prodname_actions %} 支持是有限的公测版。 [注册测试版](https://resources.github.com/beta-signup/)。 +{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." ### 延伸阅读 diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md index 549f065d12..73b218e2db 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop.md @@ -8,40 +8,40 @@ versions: free-pro-team: '*' --- -### 克隆仓库 -{% data variables.product.prodname_dotcom %} 上的仓库作为远程仓库存在。 您可以克隆其他人拥有的公共仓库。 您可以克隆自己的仓库，从而在计算机上创建本地副本，并在两个本地位置之间实现同步。 +### About local repositories +Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer. + +You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. 更多信息请参阅“[同步分支](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)”。 + +When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. 更多信息请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-forks)。” + +When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)". 也可以直接从 {% data variables.product.prodname_dotcom %} 或 {% data variables.product.prodname_enterprise %} 克隆仓库。 更多信息请参阅“[将仓库从 {% data variables.product.prodname_dotcom %} 克隆至 {% 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 %} - ![Mac 应用程序中的克隆菜单选项](/assets/images/help/desktop/clone-file-menu-mac.png) {% data reusables.desktop.cloning-location-tab %} - ![克隆仓库菜单中的 Location（位置）选项卡](/assets/images/help/desktop/choose-repository-location-mac.png) {% data reusables.desktop.cloning-repository-list %} - ![克隆仓库列表](/assets/images/help/desktop/clone-a-repository-list-mac.png) -4. 单击 **Choose...（选择...）**，并使用 Finder 窗口找到要克隆仓库的本地路径。 ![选择按钮](/assets/images/help/desktop/clone-choose-button-mac.png) -5. 单击 **Clone（克隆）**。 ![克隆按钮](/assets/images/help/desktop/clone-button-mac.png) - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.choose-clone-repository %} - ![Windows 应用程序中的克隆菜单选项](/assets/images/help/desktop/clone-file-menu-windows.png) -{% data reusables.desktop.cloning-location-tab %} - ![克隆仓库菜单中的 Location（位置）选项卡](/assets/images/help/desktop/choose-repository-location-win.png) -{% data reusables.desktop.cloning-repository-list %} - ![克隆仓库列表](/assets/images/help/desktop/clone-a-repository-list-win.png) -4. 单击 **Choose...（选择...）**，并使用 Windows 资源管理器找到要克隆仓库的本地路径。 ![选择按钮](/assets/images/help/desktop/clone-choose-button-win.png) -5. 单击 **Clone（克隆）**。 ![克隆按钮](/assets/images/help/desktop/clone-button-win.png) - -{% endwindows %} +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} ### 复刻仓库 -要对您没有写入权限的项目做出贡献，可以使用 {% data variables.product.prodname_desktop %} 创建仓库分支。 分支上的变更不会影响原始仓库。 您可以提交分支上的变更，然后将拉取请求对含有提议变更的原始仓库开放。 更多信息请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-forks)。” +If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork. -1. 如果您克隆了自己没有写入权限的仓库，并查实提交变更。{% data variables.product.prodname_desktop %} 将警告您“您对 **REPOSITORY（仓库）**没有写入权限。 单击 **create a fork（创建分支）**。 ![创建分支链接](/assets/images/help/desktop/create-a-fork.png) -3. 单击 **Fork this repository（复刻此仓库）**。 ![复刻此仓库按钮](/assets/images/help/desktop/fork-this-repo-button.png) -4. 要查看 {% data variables.product.prodname_dotcom %} 上的分支，请在 {% data variables.product.prodname_dotcom %} 右上角单击个人资料照片，然后再单击 **Your repositories（您的仓库）**。 ![您的仓库链接](/assets/images/help/profile/your-repositories.png) +{% data reusables.desktop.choose-clone-repository %} +{% data reusables.desktop.cloning-location-tab %} +{% data reusables.desktop.cloning-repository-list %} +{% data reusables.desktop.choose-local-path %} +{% data reusables.desktop.click-clone %} +{% data reusables.desktop.fork-type-prompt %} + +### Managing fork behavior +You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}. + +{% data reusables.desktop.open-repository-settings %} +{% data reusables.desktop.select-fork-behavior %} + +### 延伸阅读 +- [关于远程仓库](/github/using-git/about-remote-repositories) diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md index 8b28df3c07..25ae0412f8 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-tags.md @@ -9,7 +9,7 @@ versions: ### 关于 {% data variables.product.prodname_desktop %} 中的标记 -{% data variables.product.prodname_desktop %} 可用于创建带注释的标记。 您可以使用标记在仓库的历史记录中标记单独的点，包括发行版的版本号。 有关发行版标记的更多信息，请参阅“[关于发行版](/github/administering-a-repository/about-releases)。” +{% data variables.product.prodname_desktop %} 可用于创建带注释的标记。 Tags are associated with commits, so you can use a tag to mark an individual point in your repository's history, including a version number for a release. 有关发行版标记的更多信息，请参阅“[关于发行版](/github/administering-a-repository/about-releases)。” {% data reusables.desktop.tags-push-with-commits %} @@ -44,3 +44,7 @@ versions: {% data reusables.desktop.history-tab %} {% data reusables.desktop.delete-tag %} + +### 延伸阅读 + +- "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation diff --git a/translations/zh-CN/content/developers/apps/activating-beta-features-for-apps.md b/translations/zh-CN/content/developers/apps/activating-beta-features-for-apps.md index 85df970947..b5f581db9a 100644 --- a/translations/zh-CN/content/developers/apps/activating-beta-features-for-apps.md +++ b/translations/zh-CN/content/developers/apps/activating-beta-features-for-apps.md @@ -3,6 +3,8 @@ title: 激活应用程序的测试版功能 intro: '您可以在 {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_app %} 的公开测试版中测试所发布的新应用程序功能。' versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% warning %} diff --git a/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md b/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md index edc5993b54..26b894b487 100644 --- a/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md @@ -110,7 +110,7 @@ $ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github ```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" + "documentation_url": "{% data variables.product.doc_url_pre %}" } ``` diff --git a/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md b/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md index b2a4591235..7abf0d62c9 100644 --- a/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md +++ b/translations/zh-CN/content/developers/apps/creating-a-github-app-using-url-parameters.md @@ -60,7 +60,7 @@ versions: | [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | 授予对[电子邮件 API](/rest/reference/users#emails) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} | [`关注者`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | 授予对[关注者 API](/rest/reference/users#followers) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | | [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | 授予对[GPG 密钥 API](/rest/reference/users#gpg-keys) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | 授予对[议题 API](/rest/reference/issues) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`议题`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | 授予对[议题 API](/rest/reference/issues) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | | [`键`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | 授予对[公钥 API](/rest/reference/users#keys) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | | [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | 授予管理组织成员的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% if currentVersion == "free-pro-team@latest" %} | [`元数据`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | 授予对不泄漏敏感数据的只读端点的访问权限。 可以是 `read` 或 `none`。 设置任何权限时，默认值为 `read`；没有为 {% data variables.product.prodname_github_app %} 指定任何权限时，默认值为 `none`。 | @@ -78,7 +78,7 @@ versions: | [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | 授予对[代码扫描 API](/rest/reference/code-scanning/) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | 授予对[内容 API](/rest/reference/repos#contents) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | | [`标星`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | 授予对[标星 API](/rest/reference/activity#starring) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | 授予对[状态 API](/rest/reference/repos#statuses) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`状态`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | 授予对[状态 API](/rest/reference/repos#statuses) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | | [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | 授予对[团队讨论 API](/rest/reference/teams#discussions) 和[团队讨论注释 API](/rest/reference/teams#discussion-comments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@1.19" %} | `vulnerability_alerts` | 授予接收仓库漏洞依赖项安全警报的权限。 更多信息请参阅“[关于漏洞依赖项安全警报](/articles/about-security-alerts-for-vulnerable-dependencies)”。 可以是以下项之一：`none` 或 `read`。{% endif %} | `关注` | 授予列出和更改用户订阅的仓库的权限。 可以是以下项之一：`none`、`read` 或 `write`。 | @@ -97,8 +97,8 @@ versions: | [`deployment_status`](/webhooks/event-payloads/#deployment_status) | `部署` | {% data reusables.webhooks.deployment_status_short_desc %} | [`复刻`](/webhooks/event-payloads/#fork) | `内容` | {% data reusables.webhooks.fork_short_desc %} | [`gollum`](/webhooks/event-payloads/#gollum) | `内容` | {% 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 %} +| [`议题`](/webhooks/event-payloads/#issues) | `议题` | {% data reusables.webhooks.issues_short_desc %} +| [`issue_comment`](/webhooks/event-payloads/#issue_comment) | `议题` | {% data reusables.webhooks.issue_comment_short_desc %} | [`标签`](/webhooks/event-payloads/#label) | `元数据` | {% data reusables.webhooks.label_short_desc %} | [`成员`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %} | [`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %} @@ -117,7 +117,7 @@ versions: | [`发行版`](/webhooks/event-payloads/#release) | `内容` | {% data reusables.webhooks.release_short_desc %} | [`仓库`](/webhooks/event-payloads/#repository) | `元数据` | {% data reusables.webhooks.repository_short_desc %}{% if currentVersion == "free-pro-team@latest"%} | [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `内容` | 允许集成者使用 GitHub 操作触发自定义事件。{% endif %} -| [`状态`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %} +| [`状态`](/webhooks/event-payloads/#status) | `状态` | {% data reusables.webhooks.status_short_desc %} | [`团队`](/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 %} | [`查看`](/webhooks/event-payloads/#watch) | `元数据` | {% data reusables.webhooks.watch_short_desc %} diff --git a/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md b/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md index a3c961420e..fd56ae29f6 100644 --- a/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/zh-CN/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### 简介 -本指南将介绍 [Github 应用程序](/apps/)和[检查 API](/rest/reference/checks)，您将使用它们来构建运行测试的持续集成 (CI) 服务器。 +This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. CI 是一种需要频繁提交代码到共享仓库的软件实践。 频繁提交代码能较早检测到错误，减少在查找错误来源时开发者需要调试的代码量。 频繁的代码更新也更便于从软件开发团队的不同成员合并更改。 这对开发者非常有益，他们可以将更多时间用于编写代码，而减少在调试错误或解决合并冲突上所花的时间。 🙌 @@ -49,7 +49,7 @@ _检查套件_是一组_检查运行_（单个 CI 测试）。 套件和运行 ### 基本要求 -在开始之前，如果您尚未熟悉 [Github 应用程序](/apps/)、[web 挂钩](/webhooks)和[检查 API](/rest/reference/checks)，可能需要先熟悉一下。 您将在 [REST API 文档](/rest)中找到更多 API。 检查 API 也可用于 [GraphQL](/graphql)，但本快速入门指南侧重于 REST。 更多信息请参阅 GraphQL [检查套件](/graphql/reference/objects#checksuite)和[检查运行](/graphql/reference/objects#checkrun)对象。 +Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. 您将在 [REST API 文档](/rest)中找到更多 API。 检查 API 也可用于 [GraphQL](/graphql)，但本快速入门指南侧重于 REST。 更多信息请参阅 GraphQL [检查套件](/graphql/reference/objects#checksuite)和[检查运行](/graphql/reference/objects#checkrun)对象。 您将使用 [Ruby 编程语言](https://www.ruby-lang.org/en/)、[Smee](https://smee.io/) web 挂钩有效负载交付服务、用于 GitHub REST API 的 [Octokit.rb Ruby 库](http://octokit.github.io/octokit.rb/)以及 [Sinatra web 框架](http://sinatrarb.com/)来创建检查 API CI 服务器应用程序。 @@ -203,7 +203,7 @@ $ ruby template_server.rb ### 步骤 1.4. 更新检查运行 -当 `create_check_run` 方法运行时，它会要求 GitHub 创建新的检查运行。 当 Github 完成创建检查运行时，您将收到带有 `created` 操作的 `check_run` web 挂钩事件。 该事件是您开始运行检查的信号。 +当 `create_check_run` 方法运行时，它会要求 GitHub 创建新的检查运行。 When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. 该事件是您开始运行检查的信号。 您需要更新事件处理程序以查找 `created` 操作。 在更新事件处理程序时，可以为 `rerequested` 操作添加条件。 当某人通过单击“Re-run（重新运行）”按钮在 GitHub 上重新运行单个测试时，GitHub 将 `rerequested` 检查运行事件发送到您的应用程序。 当检查运行为 `rerequested` 时，您需要启动整个进程并创建新的检查运行。 diff --git a/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md index 6cabfa43e9..f0423e2ddd 100644 --- a/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -52,7 +52,7 @@ GitHub 应用程序使用[滑动速率限制规则](/apps/building-github-apps/u #### 注册新的 GitHub 应用程序 -一旦决定要切换到 Github 应用程序，就需要[创建新的 GitHub 应用程序](/apps/building-github-apps/)。 +Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). #### 确定应用程序所需的权限 @@ -62,7 +62,7 @@ GitHub 应用程序使用[滑动速率限制规则](/apps/building-github-apps/u #### 订阅 web 挂钩 -创建新的 GitHub 应用程序并选择其权限后，您可以选择要它订阅的 web 挂钩事件。 有关如何订阅 web 挂钩，请参阅“[编辑 GitHub 应用程序的权限](/apps/managing-github-apps/editing-a-github-app-s-permissions/)”。 +创建新的 GitHub 应用程序并选择其权限后，您可以选择要它订阅的 web 挂钩事件。 See "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. #### 了解不同的身份验证方法 diff --git a/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md b/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md index 102819caf1..6a921c856b 100644 --- a/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md +++ b/translations/zh-CN/content/developers/apps/refreshing-user-to-server-access-tokens.md @@ -42,7 +42,7 @@ versions: { "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", + "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c", "refresh_token_expires_in": "15811200", "scope": "", "token_type": "bearer" diff --git a/translations/zh-CN/content/developers/apps/suspending-a-github-app-installation.md b/translations/zh-CN/content/developers/apps/suspending-a-github-app-installation.md index 325b1a04fa..655d033bf4 100644 --- a/translations/zh-CN/content/developers/apps/suspending-a-github-app-installation.md +++ b/translations/zh-CN/content/developers/apps/suspending-a-github-app-installation.md @@ -5,6 +5,8 @@ redirect_from: - /apps/managing-github-apps/suspending-a-github-app-installation versions: free-pro-team: '*' + enterprise-server: '>=2.22' + github-ae: '*' --- {% note %} diff --git a/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index 0f495b88fc..7e1a4a81ba 100644 --- a/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -14,7 +14,7 @@ versions: {% warning %} -如果在 {% data variables.product.prodname_marketplace %} 中提供 GitHub 应用程序，您的应用程序必须按照 OAuth 授权流程来识别用户。 您不需要设置单独的 OAuth 应用程序来支持此流程。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 +If you offer a {% data variables.product.prodname_github_app %} in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate {% data variables.product.prodname_oauth_app %} to support this flow. See "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endwarning %} @@ -24,7 +24,7 @@ versions: 客户通过单击 **Complete order and begin installation（完成订单并开始安装）**来完成购买。 -然后，GitHub 将带有 `purchased` 操作的 [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) web 挂钩发送到您的应用程序。 +{% data variables.product.product_name %} then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. 从 `marketplace_purchase` web 挂钩读取 `effective_date` 和 `marketplace_purchase` 对象，以确定客户购买了哪个计划、何时开始结算周期以及何时开始下一个结算周期。 @@ -34,27 +34,27 @@ versions: ### 步骤 2. 安装 -如果您的应用程序是 GitHub 应用程序，GitHub 会在客户购买时提示客户选择应用程序可以访问的仓库。 然后，GitHub 将应用程序安装在客户选择的帐户上，并授予对所选仓库的访问权限。 +If your app is a {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} prompts the customer to select which repositories the app can access when they purchase it. {% data variables.product.product_name %} then installs the app on the account the customer selected and grants access to the selected repositories. -如果您在 GitHub 应用程序设置中指定了**设置 URL**，此时 GitHub 会将客户重定向到该 URL。 如果未指定设置 URL，您将无法处理 GitHub 应用程序的购买。 +At this point, if you specified a **Setup URL** in your {% data variables.product.prodname_github_app %} settings, {% data variables.product.product_name %} will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your {% data variables.product.prodname_github_app %}. {% note %} -**注：****设置 URL** 在 GitHub 应用程序设置中被描述为可选项，但如果您要在 {% data variables.product.prodname_marketplace %} 中提供应用程序，则它为必填字段。 +**Note:** The **Setup URL** is described as optional in {% data variables.product.prodname_github_app %} settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. {% endnote %} -如果您的应用程序是 OAuth 应用程序，GitHub 不会在任何地方安装它。 GitHub 会将客户重定向到您在 [{% data variables.product.prodname_marketplace %} 上架信息](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls)中指定的**安装 URL**。 +If your app is an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} does not install it anywhere. Instead, {% data variables.product.product_name %} redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). -当客户购买 OAuth 应用程序时，GitHub 会将客户重定向到您选择的 URL（设置 URL 或安装 URL），并且该 URL 将客户选择的定价计划包含为查询参数：`marketplace_listing_plan_id`。 +When a customer purchases an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. ### 步骤 3. 授权 当客户购买您的应用程序时，您必须通过 OAuth 授权流程发送客户： -* 如果您的应用程序是 GitHub 应用程序，则在 GitHub 将客户重定向到**设置 URL** 时开始授权流程。 请遵循“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”中的步骤。 +* If your app is a {% data variables.product.prodname_github_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -* 如果您的应用程序是 OAuth 应用程序，则在 GitHub 将客户重定向到**安装 URL** 时开始授权流程。 请遵循“[授权 OAuth 应用程序](/apps/building-oauth-apps/authorizing-oauth-apps/)”中的步骤。 +* If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)." 对于任一类型的应用程序，第一步都是将客户重定向到 https://github.com/login/oauth/authorize。 diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md index de115a2808..7c995e802c 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -499,7 +499,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {{ webhookPayloadsForCurrentVersion.issue_comment.created }} -### issues +### 议题 {% data reusables.webhooks.issues_short_desc %} diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md index 2f09b5f55e..0a9fb05560 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -16,7 +16,7 @@ Repl.it 是一个支持多种编程语言的在线集成开发环境 (IDE)。 学生第一次单击按钮访问 Repl.it 时，必须使用 {% data variables.product.product_name %} 证书登录 Repl.it。 登录后，学生将有权访问包含作业仓库中代码、在 Repl.it 上完全配置的开发环境。 -有关操作 Repl.it 的更多信息，请参阅 [Repl.it 快速入门指南](https://docs.repl.it/misc/quick-start#the-repl-environment)。 +有关操作 Repl.it 的更多信息，请参阅 [Repl.it 快速入门指南](https://docs.repl.it/repls/quick-start#the-repl-environment)。 对于小组作业，学生可以使用 Repl.it Multiplayer 协同工作。 更多信息请参阅 [Repl.it Multiplayer](https://repl.it/site/multiplayer) 网站。 diff --git a/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md index c49dbf391f..0808ddaba9 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -3,6 +3,7 @@ title: 关于 Dependabot 版本更新 intro: '您可以使用 {% data variables.product.prodname_dependabot %} 来确保您使用的包更新到最新版本。' redirect_from: - /github/administering-a-repository/about-dependabot + - /github/administering-a-repository/about-github-dependabot - /github/administering-a-repository/about-github-dependabot-version-updates versions: free-pro-team: '*' @@ -14,9 +15,9 @@ versions: {% data variables.product.prodname_dependabot %} 负责维护您的依赖项。 您可以使用它来确保仓库自动跟上它所依赖的包和应用程序的最新版本。 -通过将配置文件检入仓库，可启用 {% data variables.product.prodname_dependabot_version_updates %}。 配置文件指定存储在仓库中的清单或其他包定义文件的位置。 {% data variables.product.prodname_dependabot %} 使用此信息来检查过时的软件包和应用程序。 {% data variables.product.prodname_dependabot %} 确定依赖项是否有新版本，它通过查看依赖的语义版本 ([semver](https://semver.org/)) 来决定是否应更新该版本。 对于某些软件包管理器，{% data variables.product.prodname_dependabot_version_updates %} 也支持供应。 供应（或缓存）的依赖项是检入仓库中特定目录的依赖项，而不是在清单中引用的依赖项。 即使包服务器不可用，供应的依赖项在生成时也可用。 {% data variables.product.prodname_dependabot_version_updates %} 可以配置为检查为新版本供应的依赖项，并在必要时更新它们。 +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} 使用此信息来检查过时的软件包和应用程序。 {% data variables.product.prodname_dependabot %} 确定依赖项是否有新版本，它通过查看依赖的语义版本 ([semver](https://semver.org/)) 来决定是否应更新该版本。 对于某些软件包管理器，{% data variables.product.prodname_dependabot_version_updates %} 也支持供应。 Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. 即使包服务器不可用，供应的依赖项在生成时也可用。 {% data variables.product.prodname_dependabot_version_updates %} 可以配置为检查为新版本供应的依赖项，并在必要时更新它们。 -当 {% data variables.product.prodname_dependabot %} 发现过时的依赖项时，它会发起拉取请求以将清单更新到依赖项的最新版本。 对于供应和依赖项，{% data variables.product.prodname_dependabot %} 提出拉取请求以直接将过时的依赖项替换为新版本。 检查测试是否通过，查看拉取请求摘要中包含的更改日志和发行说明，然后合并它。 更多信息请参阅“[启用和禁用版本更新](/github/administering-a-repository/enabling-and-disabling-version-updates)”。 +当 {% data variables.product.prodname_dependabot %} 发现过时的依赖项时，它会发起拉取请求以将清单更新到依赖项的最新版本。 For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. 检查测试是否通过，查看拉取请求摘要中包含的更改日志和发行说明，然后合并它。 更多信息请参阅“[启用和禁用版本更新](/github/administering-a-repository/enabling-and-disabling-version-updates)”。 如果启用安全更新，{% data variables.product.prodname_dependabot %} 还会发起拉取请求以更新易受攻击依赖项。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。 diff --git a/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md b/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md index f29845fe8e..a73e0a628c 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-protected-branches.md @@ -84,11 +84,11 @@ remote: error: Changes have been requested. 您可以将必需状态检查设置为“宽松”或“严格”。 您选择的必需状态检查类型确定合并之前是否需要使用基础分支将您的分支保持最新状态。 -| 必需状态检查的类型 | 设置 | 合并要求 | 考虑因素 | -| --------- | ------------------------------------------------------------------------------- | ---------------------------- | ----------------------------------------------------------------------------- | -| **严格** | 选中 **Require branches to be up-to-date before merging（合并前需要分支保持最新状态）**复选框。 | 在合并之前，**必须**使用基础分支使分支保持最新状态。 | 这是必需状态检查的默认行为。 可能需要更多构建，因为在其他协作者将拉取请求合并到受保护基础分支后，您需要使头部分支保持最新状态。 | -| **宽松** | **不**选中 **Require branches to be up-to-date before merging（合并前需要分支保持最新状态）**复选框。 | 在合并之前，**不**必使用基础分支使分支保持最新状态。 | 您将需要更少的构建，因为在其他协作者合并拉取请求后，您不需要使头部分支保持最新状态。 如果存在与基础分支不兼容的变更，则在合并分支后，状态检查可能会失败。 | -| **已禁用** | **不**选中 **Require status checks to pass before merging（合并前需要状态检查通过）**复选框。 | 分支没有合并限制。 | 如果未启用必需状态检查，协作者可以随时合并分支，无论它是否使用基础分支保持最新状态。 这增加了不兼容变更的可能性。 | +| 必需状态检查的类型 | 设置 | 合并要求 | 考虑因素 | +| --------- | ------------------------------------------------------------------------------------- | ---------------------------- | ----------------------------------------------------------------------------- | +| **严格** | The **Require branches to be up to date before merging** checkbox is checked. | 在合并之前，**必须**使用基础分支使分支保持最新状态。 | 这是必需状态检查的默认行为。 可能需要更多构建，因为在其他协作者将拉取请求合并到受保护基础分支后，您需要使头部分支保持最新状态。 | +| **宽松** | The **Require branches to be up to date before merging** checkbox is **not** checked. | 在合并之前，**不**必使用基础分支使分支保持最新状态。 | 您将需要更少的构建，因为在其他协作者合并拉取请求后，您不需要使头部分支保持最新状态。 如果存在与基础分支不兼容的变更，则在合并分支后，状态检查可能会失败。 | +| **已禁用** | **不**选中 **Require status checks to pass before merging（合并前需要状态检查通过）**复选框。 | 分支没有合并限制。 | 如果未启用必需状态检查，协作者可以随时合并分支，无论它是否使用基础分支保持最新状态。 这增加了不兼容变更的可能性。 | 有关故障排除信息，请参阅“[必需状态检查故障排除](/github/administering-a-repository/troubleshooting-required-status-checks)”。 diff --git a/translations/zh-CN/content/github/administering-a-repository/about-securing-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/about-securing-your-repository.md index 7f8d6a345d..3eb8f8993b 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-securing-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-securing-your-repository.md @@ -14,6 +14,8 @@ versions: {% data variables.product.prodname_dotcom %} 有越来越多的安全功能，可帮助您保护代码安全。 您可以在仓库的 **Security（安全）**选项卡上找到这些功能。 +#### Available for all repositories + {% if currentVersion == "free-pro-team@latest" %} - **安全策略** @@ -43,15 +45,23 @@ versions: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +#### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %} + +These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %} + - **{% data variables.product.prodname_code_scanning_capc %} 警报** 自动检测新代码或修改代码中的安全漏洞和编码错误。 潜在的问题被高亮显示，并附有详细信息，允许您在将代码合并到默认分支之前修复它。 更多信息请参阅“[关于代码扫描](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)”。 - **检测到的密钥** -查看 - {% data variables.product.prodname_dotcom %} 在您的代码中找到的任何密钥。 应将已检入仓库的令牌或凭据视为已泄露。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 - {% endif %} + {% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else if %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. 应将已检入仓库的令牌或凭据视为已泄露。 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 + +{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +- **依赖项审查** - 在合并拉取请求之前显示依赖项更改的全部影响以及任何有漏洞版本的详情。 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 +{% endif %} ### 探索依赖项 {% data variables.product.prodname_dotcom %} 的依赖项图允许您探索： @@ -59,6 +69,6 @@ versions: * 您的仓库依赖的生态系统和包 * 依赖于您的仓库的仓库和包 -必须先启用依赖项图，然后 {% data variables.product.prodname_dotcom %} 才能针对有安全漏洞的依赖项生成 {% data variables.product.prodname_dependabot_alerts %}。 +必须先启用依赖项图，然后 {% data variables.product.prodname_dotcom %} 才能针对有安全漏洞的依赖项生成 {% data variables.product.prodname_dependabot_alerts %}。 {% if currentVersion == "free-pro-team@latest" %}Enabling the dependency graph also enables {% data variables.product.prodname_dotcom %} to run dependency reviews of pull requests.{% endif %} 您可以在仓库的 **Insights（洞察）**选项卡上找到依赖项图。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 diff --git a/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md b/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md index e12b0e396a..04518d8843 100644 --- a/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md +++ b/translations/zh-CN/content/github/administering-a-repository/configuring-secret-scanning-for-your-repositories.md @@ -27,13 +27,13 @@ versions: {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} 4. 如果 "{% data variables.product.prodname_secret_scanning_caps %}" 未显示在页面上，您需要先启用 {% data variables.product.prodname_GH_advanced_security %}。 在“{% data variables.product.prodname_GH_advanced_security %}”右边单击 **Enable（启用）**。 ![为仓库启用 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/repository/enable-ghas-dotcom.png) 5. 单击**为此仓库启用 {% data variables.product.prodname_GH_advanced_security %}** 以确认操作。 ![确认为仓库启用 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/repository/enable-ghas-confirmation-dotcom.png) 6. 当您启用 {% data variables.product.prodname_GH_advanced_security %} 时，可能会自动为仓库启用 {% data variables.product.prodname_secret_scanning %}（这是由组织配置控制的）。 如果 "{% data variables.product.prodname_secret_scanning_caps %}" 显示 **Enable（启用）**按钮，则您仍需通过单击 **Enable（启用）**来启用 {% data variables.product.prodname_secret_scanning %}。 如果您看到 **Disable（禁用）**按钮，则表明 {% data variables.product.prodname_secret_scanning %} 已启用。 - ![为仓库启用 {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/enable-secret-scanning-dotcom.png){% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + ![为仓库启用 {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/enable-secret-scanning-dotcom.png) + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} 4. 在 " {% data variables.product.prodname_secret_scanning_caps %}" 的右侧，单击 **Enable（启用）**。 ![为仓库启用 {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/enable-secret-scanning-ghe.png) diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md index 05da1b5ce3..a1f3bef6fe 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -4,13 +4,12 @@ intro: "您可以允许或禁止仓库中拉取请求的自动合并。" product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' permissions: 具有维护员权限的人可以管理仓库中拉取请求的自动合并。 --- -{% data reusables.pull_requests.auto-merge-release-phase %} - 如果您允许自动合并仓库中的拉取请求，则用户可以配置仓库中的单个拉取请求在满足所有合并要求时自动合并。 更多信息请参阅“[自动合并拉取请求](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)”。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. 在“Merge button（合并按钮）”下，选择或取消选择 **Allow auto-merge（允许自动合并）**。 ![允许或禁止自动合并的复选框](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) \ No newline at end of file +1. 在“Merge button（合并按钮）”下，选择或取消选择 **Allow auto-merge（允许自动合并）**。 ![允许或禁止自动合并的复选框](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md index cd851305f8..f29eb0cb90 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -33,10 +33,15 @@ versions: {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} 4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。 -{% if currentVersion == "free-pro-team@latest" %}如果 "{% data variables.product.prodname_secret_scanning_caps %}" 未显示，您可能需要先启用 {% data variables.product.prodname_GH_advanced_security %}。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first. !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% note %} +**Note:** If you disable + + {% data variables.product.prodname_GH_advanced_security %}, both {% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail. + {% endnote %} + + {% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %} !["Configure security and analysis（配置安全性和分析）"功能的"Enable（启用）"或"Disable（禁用）"按钮](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghe.png) {% endif %} diff --git a/translations/zh-CN/content/github/administering-a-repository/securing-your-repository.md b/translations/zh-CN/content/github/administering-a-repository/securing-your-repository.md index bfb5c63c08..601e682d05 100644 --- a/translations/zh-CN/content/github/administering-a-repository/securing-your-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/securing-your-repository.md @@ -6,5 +6,6 @@ redirect_from: - /articles/securing-your-repository versions: free-pro-team: '*' + enterprise-server: '>=3.0' --- diff --git a/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md b/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md index aae985e75f..a9147d8e6b 100644 --- a/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md @@ -24,7 +24,7 @@ versions: * 如果您将仓库的可见性从内部更改为私有， {% data variables.product.prodname_dotcom %} 将删除属于任何没有新私有仓库访问权限的用户的复刻。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}任何复刻的可见性也将更改为私有。{% elsif currentVersion == "github-ae@latest" %}如果内部仓库有任何复刻，则复刻的可见性已经是私有的。{% endif %}更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)”{% if currentversion == "free proteam@latest" %} * 如果对用户帐户或组织使用 {% data variables.product.prodname_free_user %}，有些功能在您将可见性更改为私有后不可用于仓库。 {% data reusables.gated-features.more-info %}{% endif %} * 任何已发布的 {% data variables.product.prodname_pages %} 站点将自动取消发布。{% if currentVersion == "free-pro-team@latest" %} 如果将自定义域添加到 {% data variables.product.prodname_pages %} 站点，应先删除或更新 DNS 记录后再将仓库设为私有，以避免域接管的风险。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。{% endif %}{% if currentVersion == "free-pro-team@latest" %} -* {% data variables.product.prodname_dotcom %} 不再在 {% data variables.product.prodname_archive %} 中包含该仓库。 更多信息请参阅“[关于在 {% 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" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} +* {% data variables.product.prodname_dotcom %} 不再在 {% data variables.product.prodname_archive %} 中包含该仓库。 For more information, 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)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} * {% data variables.product.prodname_GH_advanced_security %} 功能，例如 {% data variables.product.prodname_code_scanning %}，将停止工作，除非拥有仓库的组织具有 {% data variables.product.prodname_advanced_security %} 许可。 {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %} * 匿名 Git 读取权限不再可用。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)”。{% endif %} diff --git a/translations/zh-CN/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/zh-CN/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md index 0537fad197..b05e3dee2b 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md +++ b/translations/zh-CN/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md @@ -33,14 +33,18 @@ versions: Comment: GitHub key Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? ``` -7. 输入 `O` 以保存选择。 +7. Enter `O` to confirm your selections. 8. 输入密钥的密码。 -9. 输入 `gpg --armor --export GPG key ID`，替换要使用的 GPG 密钥 ID。 在以下示例中，GPG 密钥 ID 是 `3AA5C34371567BD2`： +9. Enter `gpg> save` to save the changes + ```shell + $ gpg> save + ``` +10. 输入 `gpg --armor --export GPG key ID`，替换要使用的 GPG 密钥 ID。 在以下示例中，GPG 密钥 ID 是 `3AA5C34371567BD2`： ```shell $ gpg --armor --export 3AA5C34371567BD2 # Prints the GPG key, in ASCII armor format ``` -10. [添加 GPG 密钥到 GitHub 帐户](/articles/adding-a-new-gpg-key-to-your-github-account)以上传该 GPG 密钥。 +11. [添加 GPG 密钥到 GitHub 帐户](/articles/adding-a-new-gpg-key-to-your-github-account)以上传该 GPG 密钥。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md index d999762e33..b690852778 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md @@ -4,10 +4,9 @@ intro: '您可以通过启用拉取请求自动合并（使拉取请求在满足 product: '{% data reusables.gated-features.auto-merge %}' versions: free-pro-team: '*' + enterprise-server: '>=3.1' --- -{% data reusables.pull_requests.auto-merge-release-phase %} - ### 关于自动合并 如果启用拉取请求自动合并，则拉取请求在满足所有必需审查并且状态检查通过时将自动合并。 自动合并使您无需等待满足要求，可以继续执行其他任务。 diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md index fe77de58a8..7f54164e4f 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.md @@ -9,7 +9,6 @@ versions: github-ae: '*' --- - ### 关于拉取请求合并 在拉取请求中，您提议将您对头部分支所做的更改合并到基础分支。 默认情况下，任何拉取请求都可随时合并，除非头部分支与基本分支冲突。 但是，何时可以将拉取请求合并到特定分支中可能会有一些限制。 例如，如果必需状态检查通过，您可能只能将拉取请求合并到默认分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches)”。 diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md index 571613fad2..da0c46c88f 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests.md @@ -1,5 +1,5 @@ --- -title: 通过拉取请求提议工作更改 +title: 发起提案，请求改进项目 intro: '在添加更改到主题分支或复刻后，您可以打开拉取请求，要求协作者或仓库管理员审查您的更改，然后将其合并到项目中。' mapTopic: true redirect_from: diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md index bee5e35f90..e89442ea4b 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-code-owners.md @@ -23,7 +23,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}如果团队启用了代码审查分配，则个别审批无法满足受保护分支中代码所有者审批的要求。 更多信息请参阅“[管理团队的代码审查分配](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)”。{% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 如果文件具有代码所有者，则在打开拉取请求之前可以看到代码所有者是谁。 在仓库中，您可以浏览文件并将鼠标悬停在上方 {% octicon "shield-lock" aria-label="The edit icon" %}. diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md index ad4395527c..6d3f0f5782 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/duplicating-a-repository.md @@ -1,6 +1,6 @@ --- title: 复制仓库 -intro: '要复制存储库而不对其进行复制，可以运行特殊克隆命令，然后镜像推送到新仓库。' +intro: '要复制存储库而不对其进行复刻，可以运行特殊克隆命令，然后镜像推送到新仓库。' redirect_from: - /articles/duplicating-a-repo/ - /articles/duplicating-a-repository diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md index 7359928c50..9684696ef4 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -1,6 +1,6 @@ --- -title: 关于代码扫描 -intro: '您可以使用 {% data variables.product.prodname_code_scanning %} 在 {% data variables.product.prodname_dotcom %} 上查找项目中的安全漏洞和代码错误。' +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/managing-security-vulnerabilities/about-automated-code-scanning @@ -12,39 +12,40 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### 关于 {% data variables.product.prodname_code_scanning %} +### About {% data variables.product.prodname_code_scanning %} {% data reusables.code-scanning.about-code-scanning %} -您可以使用 {% data variables.product.prodname_code_scanning %} 来查找代码中现有的问题，并且对其进行分类和确定修复的优先级。 {% data variables.product.prodname_code_scanning_capc %} 还可防止开发者引入新问题。 您可以计划在特定的日期和时间进行扫描，或在仓库中发生特定事件（如推送）时触发扫描。 +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. -如果 {% data variables.product.prodname_code_scanning %} 发现您的代码中可能存在漏洞或错误，{% data variables.product.prodname_dotcom %} 会在仓库中显示警报。 在修复触发警报的代码之后，{% data variables.product.prodname_dotcom %} 将关闭警报。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 +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)." -要监控您的仓库或组织的 {% data variables.product.prodname_code_scanning %} 结果，您可以使用 web 挂钩和 {% data variables.product.prodname_code_scanning %} API。 有关用于 {% data variables.product.prodname_code_scanning %} 的 web 挂钩的信息，请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)”。 有关 API 端点的信息，请参阅“[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)”。 +To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see +"[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." -要开始 {% data variables.product.prodname_code_scanning %}，请参阅“[启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)”。 +To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." -### 关于 {% data variables.product.prodname_codeql %} +### About {% data variables.product.prodname_codeql %} -您可以在 [`github/codeql`](https://github.com/github/codeql) 仓库中查看并参与 {% data variables.product.prodname_code_scanning %} 的查询。 {% 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 %} 是授权 {% data variables.product.prodname_codeql %} 的查询语言。 {% data variables.product.prodname_ql %} 是一种面向对象的逻辑编程语言。 {% data variables.product.company_short %}、语言专家和安全研究人员创建用于 {% data variables.product.prodname_code_scanning %} 的查询，查询是开源的。 社区维护和更新查询，以改善分析和减少误报。 更多信息请参阅 GitHub Security Lab 网站上的 [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql)。 +{% 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 %} 的 API 端点的更多信息，请参阅“[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)”。 +{% 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 %} -您可以在 [`github/codeql`](https://github.com/github/codeql) 仓库中查看并参与 {% data variables.product.prodname_code_scanning %} 的查询。 更多信息请参阅 {% data variables.product.prodname_codeql %} 文档中的 [{% data variables.product.prodname_codeql %} 查询](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html)。 +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" %} -### 关于 {% data variables.product.prodname_code_scanning %} 的计费 +### About billing for {% data variables.product.prodname_code_scanning %} -{% data variables.product.prodname_code_scanning_capc %} 使用 {% data variables.product.prodname_actions %}，{% data variables.product.prodname_code_scanning %} 工作流程的每次运行将耗用 {% data variables.product.prodname_actions %} 的分钟数。 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)”。 +{% 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 %} @@ -52,9 +53,9 @@ versions: {% data reusables.code-scanning.get-started-uploading-third-party-data %} -### 延伸阅读 +### Further reading {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} - [{% data variables.product.prodname_security %}](https://securitylab.github.com/) -- OASIS Committee 网站上的 [OASIS 静态分析结果交换格式 (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) +- [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/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md index 34e56b50c8..c3c9321083 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md @@ -135,19 +135,22 @@ $ /path/to-runner/codeql-runner-linux autobuild --language csharp 分析 {% data variables.product.prodname_codeql %} 数据库中的代码并将结果上传到 {% data variables.product.product_location %}。 -| 标志 | 必选 | 输入值 | -| -------------------------------- |:--:| --------------------------------------------------------------------------------------------------------------------------------- | -| `--repository` | ✓ | 要分析的仓库名称。 | -| `--commit` | ✓ | 要分析的提交的 SHA。 在 Git 和 Azure DevOps 中，这对应于 `git rev-parse HEAD` 的值。 在 Jenkins 中，这对应于 `$GIT_COMMIT`。 | -| `--ref` | ✓ | 要分析的引用的名称，例如 `refs/heads/main`。 在 Git 和 Jenkins 中，这对应于 `git symbolic-ref HEAD` 的值。 在 Azure DevOps 中，这对应于 `$(Build.SourceBranch)`。 | -| `--github-url` | ✓ | 托管仓库的 {% data variables.product.prodname_dotcom %} 实例的 URL。 | -| `--github-auth` | ✓ | {% data variables.product.prodname_github_apps %} 令牌或个人访问令牌。 | -| `--checkout-path` | | 检出仓库的路径。 默认值为当前工作目录。 | -| `--no-upload` | | 无. 阻止 {% data variables.product.prodname_codeql_runner %} 将结果上传到 {% data variables.product.product_location %}。 | -| `--output-dir` | | 存储输出 SARIF 文件的目录。 默认在临时文件目录中。 | -| `--temp-dir` | | 存储临时文件的目录。 默认值为 _./codeql-runner_。 | -| `--debug` | | 无. 打印更详细的输出。 | -| `-h`, `--help` | | 无. 显示命令的帮助。 | +| 标志 | 必选 | 输入值 | +| ---------------------------------- |:--:| --------------------------------------------------------------------------------------------------------------------------------- | +| `--repository` | ✓ | 要分析的仓库名称。 | +| `--commit` | ✓ | 要分析的提交的 SHA。 在 Git 和 Azure DevOps 中，这对应于 `git rev-parse HEAD` 的值。 在 Jenkins 中，这对应于 `$GIT_COMMIT`。 | +| `--ref` | ✓ | 要分析的引用的名称，例如 `refs/heads/main`。 在 Git 和 Jenkins 中，这对应于 `git symbolic-ref HEAD` 的值。 在 Azure DevOps 中，这对应于 `$(Build.SourceBranch)`。 | +| `--github-url` | ✓ | 托管仓库的 {% data variables.product.prodname_dotcom %} 实例的 URL。 | +| `--github-auth` | ✓ | {% data variables.product.prodname_github_apps %} 令牌或个人访问令牌。 | +| `--checkout-path` | | 检出仓库的路径。 默认值为当前工作目录。 | +| `--no-upload` | | 无. 阻止 {% data variables.product.prodname_codeql_runner %} 将结果上传到 {% data variables.product.product_location %}。 | +| `--output-dir` | | 存储输出 SARIF 文件的目录。 默认在临时文件目录中。 | +| `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. | +| `--no-add-snippets` | | 无. Excludes code snippets from the SARIF output. | +| `--threads` | | Number of threads to use when running queries. The default is to use all available cores. | +| `--temp-dir` | | 存储临时文件的目录。 默认值为 _./codeql-runner_。 | +| `--debug` | | 无. 打印更详细的输出。 | +| `-h`, `--help` | | 无. 显示命令的帮助。 | #### `上传` diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md index 411391e517..3a1a134855 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages.md @@ -17,7 +17,7 @@ versions: ### 关于 {% data variables.product.prodname_codeql_workflow %} 和编译语言 -To enable {% data variables.product.prodname_code_scanning %} for your repository, you add to the repository a {% data variables.product.prodname_actions %} workflow which includes {% data variables.product.prodname_codeql %} analysis. 更多信息请参阅“[启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)”。 对于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}，您可以添加 {% data variables.product.prodname_codeql_workflow %}。 默认 {% data variables.product.prodname_code_scanning %} 工作流程使用 `on.push` 事件触发代码扫描 - 每次推送到任何包含工作流程文件的分支时触发。 +You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. 对于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}，您可以添加 {% data variables.product.prodname_codeql_workflow %}。 For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data reusables.code-scanning.edit-workflow %} 有关配置 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md index 3181219cee..78c292bc1e 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md @@ -14,7 +14,7 @@ versions: {% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %} {% link_in_list /about-code-scanning %} {% link_in_list /triaging-code-scanning-alerts-in-pull-requests %} - {% link_in_list /enabling-code-scanning %} + {% link_in_list /setting-up-code-scanning-for-a-repository %} {% link_in_list /managing-code-scanning-alerts-for-your-repository %} {% link_in_list /configuring-code-scanning %} {% link_in_list /configuring-the-codeql-workflow-for-compiled-languages %} diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md index 2a46d7a8fa..c72d66e497 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md @@ -16,7 +16,7 @@ redirect_from: ### 关于 {% data variables.product.prodname_code_scanning %} 中的警报 -您可以设置 {% data variables.product.prodname_code_scanning %}，以使用默认 {% data variables.product.prodname_codeql %} 分析、第三方分析或多种类型的分析来检查仓库中的代码。 分析完成后，生成的警报将并排显示在仓库的安全视图中。 第三方工具或自定义查询的结果可能不包括您在 {% data variables.product.company_short %} 的默认 {% data variables.product.prodname_codeql %} 分析所检测的警报中看到的所有属性。 默认 {% data variables.product.prodname_code_scanning %} 工作流程使用 `on.push` 事件触发代码扫描 - 每次推送到任何包含工作流程文件的分支时触发。 +您可以设置 {% data variables.product.prodname_code_scanning %}，以使用默认 {% data variables.product.prodname_codeql %} 分析、第三方分析或多种类型的分析来检查仓库中的代码。 分析完成后，生成的警报将并排显示在仓库的安全视图中。 第三方工具或自定义查询的结果可能不包括您在 {% data variables.product.company_short %} 的默认 {% data variables.product.prodname_codeql %} 分析所检测的警报中看到的所有属性。 For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." 默认情况下， {% data variables.product.prodname_code_scanning %} 定期在默认分支和拉取请求中分析您的代码。 有关管理拉取请求中的警报的更多信息，请参阅“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)”。 @@ -28,7 +28,7 @@ redirect_from: ![来自 {% data variables.product.prodname_code_scanning %} 的警报示例](/assets/images/help/repository/code-scanning-alert.png) -如果使用 {% data variables.product.prodname_codeql %} 启用 {% data variables.product.prodname_code_scanning %}，也可以检测代码中的数据流问题。 数据流分析将查找代码中的潜在安全问题，例如：不安全地使用数据、将危险参数传递给函数以及泄漏敏感信息。 +If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. 数据流分析将查找代码中的潜在安全问题，例如：不安全地使用数据、将危险参数传递给函数以及泄漏敏感信息。 当 {% data variables.product.prodname_code_scanning %} 报告数据流警报时，{% data variables.product.prodname_dotcom %} 将显示数据在代码中如何移动。 {% data variables.product.prodname_code_scanning_capc %} 可用于识别泄露敏感信息的代码区域，以及可能成为恶意用户攻击切入点的代码区域。 @@ -65,7 +65,7 @@ redirect_from: ### 忽略或删除警报 -有两种方法可以关闭警报。 您可以修复代码中的问题，也可以忽略警报。 或者，如果您具有仓库的管理员权限，您可以删除警报。 删除警报适用于以下情况：您启用了 {% data variables.product.prodname_code_scanning %} 工具，然后决定删除它，或者您启用了 {% data variables.product.prodname_codeql %} 分析，但查询集超出您的需求，于是您从工具中删除了某些查询。 在这两种情况下，删除警报允许您清理 {% data variables.product.prodname_code_scanning %} 结果。 您可以在 **Security（安全）**选项卡中从摘要列表删除警报。 +有两种方法可以关闭警报。 您可以修复代码中的问题，也可以忽略警报。 或者，如果您具有仓库的管理员权限，您可以删除警报。 Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. 在这两种情况下，删除警报允许您清理 {% data variables.product.prodname_code_scanning %} 结果。 您可以在 **Security（安全）**选项卡中从摘要列表删除警报。 忽略警报是关闭您认为不需要修复的警报的一种方式。 {% data reusables.code-scanning.close-alert-examples %} 您可以从代码中的 {% data variables.product.prodname_code_scanning %} 注释忽略警报，或者从 **Security（安全）**选项卡中的摘要列表忽略警报。 @@ -127,5 +127,5 @@ redirect_from: ### 延伸阅读 - “[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)” -- “[为仓库启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)” +- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)" - "[关于与 {% data variables.product.prodname_code_scanning %} 集成](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)" diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 519f8796c6..f096fdc9d2 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -24,7 +24,7 @@ versions: {% data reusables.code-scanning.about-code-scanning %} 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)”。 -您可以使用 {% data variables.product.prodname_codeql_runner %} 在第三方持续集成 (CI) 系统中处理的代码上运行 {% data variables.product.prodname_code_scanning %}。 您也可以使用 {% data variables.product.prodname_actions %} 在 {% data variables.product.product_location %} 上运行 {% data variables.product.prodname_code_scanning %}。 更多信息请参阅“[为仓库启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)”。 +您可以使用 {% data variables.product.prodname_codeql_runner %} 在第三方持续集成 (CI) 系统中处理的代码上运行 {% data variables.product.prodname_code_scanning %}。 您也可以使用 {% data variables.product.prodname_actions %} 在 {% data variables.product.product_location %} 上运行 {% data variables.product.prodname_code_scanning %}。 For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)." {% data variables.product.prodname_codeql_runner %} 是在 {% data variables.product.prodname_dotcom %} 仓库的检出上运行 {% data variables.product.prodname_codeql %} 分析的命令行工具。 您可以将运行器添加到第三方系统，然后调用运行器以分析代码并将结果上传到 {% data variables.product.product_location %}。 这些结果在仓库中显示为 {% data variables.product.prodname_code_scanning %} 警报。 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index ca00fde0d5..604affed30 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -97,7 +97,6 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS | `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)。 | -| `suppressions[].state` | **可选。**当 `state` 设置为 `accepted` 时，{% data variables.product.prodname_code_scanning %} 将在 {% data variables.product.prodname_dotcom %} 上将结果的状态更新为 `Closed`。 | #### `location` 对象 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md new file mode 100644 index 0000000000..8db47721fe --- /dev/null +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository.md @@ -0,0 +1,117 @@ +--- +title: Setting up code scanning for a repository +shortTitle: Setting up code scanning +intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.' +product: '{% data reusables.gated-features.code-scanning %}' +permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.' +redirect_from: + - /github/managing-security-vulnerabilities/configuring-automated-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning + - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} + +### Options for setting up {% data variables.product.prodname_code_scanning %} + +You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to use, at a repository level. {% data variables.product.product_name %} 对 {% data variables.product.prodname_codeql %} 分析提供完全集成的支持，还支持使用第三方工具进行分析。 更多信息请参阅“[关于 {% 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 %} + +### Setting up {% data variables.product.prodname_code_scanning %} using actions + +{% if currentVersion == "free-pro-team@latest" %}使用操作运行 {% data variables.product.prodname_code_scanning %} 需时数分钟。 更多信息请参阅“[关于 {% 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 "Code scanning", click **Set up code scanning**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@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](/github/setting-up-and-managing-organizations-and-teams/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 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 code scanning" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png) +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 %} 而不对其做任何更改。 但是，许多第三方工作流程需要额外的配置，因此在提交之前请阅读工作流程中的注释。 + + 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)。” +6. 使用 **Start commit（开始提交）**下拉菜单，并键入提交消息。 ![开始提交](/assets/images/help/repository/start-commit-commit-new-file.png) +7. 选择您是想直接提交到默认分支，还是创建新分支并启动拉取请求。 ![选择提交位置](/assets/images/help/repository/start-commit-choose-where-to-commit.png) +8. 单击 **Commit new file（提交新文件）**或 **Propose new file（提议新文件）**。 + +在默认 {% data variables.product.prodname_codeql_workflow %} 中，{% data variables.product.prodname_code_scanning %} 配置为在每次将更改推送到默认分支或任何受保护分支或者对默认分支提出拉取请求时分析代码。 因此，{% data variables.product.prodname_code_scanning %} 将立即开始。 + +### 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. 有关提出拉取请求以向多个仓库添加 {% data variables.product.prodname_actions %} 工作流程的脚本示例，请参阅 [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) 仓库。 + +### 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)." + +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 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 %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/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_ 条警报**链接。 + + ![点击"发现的 n 条警报"链接](/assets/images/help/repository/code-scanning-alerts-found-link.png) + +{% endnote %} + +### 了解拉取请求检查 + +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. 工作流程中每个分析作业有一个条目，最后还有一个对应于分析结果的条目。 + +{% data variables.product.prodname_code_scanning %} 分析检查的名称采用形式："TOOL NAME / JOB NAME (TRIGGER)"。 例如，对于 {% data variables.product.prodname_codeql %}，C++ 代码的分析有条目 "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)"。 您可以单击 {% data variables.product.prodname_code_scanning %} 分析条目上的**Details（详细信息）**来查看日志记录数据。 这允许您在分析作业失败时调试问题。 例如，对于编译的语言的 {% data variables.product.prodname_code_scanning %} 分析，如果操作无法生成代码，则可能会发生这种情况。 + + ![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（缺少分析）”的消息。 + + ![缺少提交消息的分析](/assets/images/help/repository/code-scanning-missing-analysis.png) + +#### “缺少分析”消息的原因 + +在 {% 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 的分析）”消息。 + +在其他情况下，可能没有分析对拉取请求的基础分支的最新提交。 这些包括： + +* 已针对默认分支以外的分支提出拉取请求，并且尚未分析此分支。 + + 要检查是否扫描了分支，请转到 {% data variables.product.prodname_code_scanning_capc %} 页面，单击 **Branch<（分支）**下拉菜单并选择相关分支。 + + ![从 Branch（分支）下拉菜单中选择一个分支](/assets/images/help/repository/code-scanning-branch-dropdown.png) + + {% 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 variables.product.prodname_code_scanning %}。 + +* 在分析基础分支上的最新提交时发生了错误，且该提交的分析不可用。 + + 将一个微小的更改合并到基础分支以触发此最新提交的 {% data variables.product.prodname_code_scanning %}，然后将更改推送到拉取请求以重新触发 {% data variables.product.prodname_code_scanning %}。 + +### 后续步骤 + +After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: + +- 查看为此仓库生成的所有 {% data variables.product.prodname_code_scanning %} 警报。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/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 set up {% data variables.product.prodname_code_scanning %}. 更多信息请参阅“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)”。 +- 为已完成的运行设置通知。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)”。 +- 调查初始设置 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 时发生的任何问题。 更多信息请参阅“[{% data variables.product.prodname_codeql %} 工作流程疑难解答](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)”。 +- 自定义 {% data variables.product.prodname_code_scanning %} 如何扫描您的仓库中的代码。 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)。” diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md index ea7682afc7..c2b95a7810 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests.md @@ -15,7 +15,7 @@ versions: 在仓库中，如果 {% 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 %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 -如果 {% data variables.product.prodname_code_scanning %} 有任何严重性为 `error` 的结果，则检查失败，错误将报告在检查结果中。 如果 {% data variables.product.prodname_code_scanning %} 发现的所有结果的严重性都较低，则警报将被视为警告或通知，检查成功。 如果拉取请求针对已为 {% data variables.product.prodname_code_scanning %} 启用的受保护分支，并且仓库所有者配置了必需状态检查，则您必须修复或{% if currentVersion == "enterprise-server@2.22" %}关闭{% else %}忽略{% endif %}所有错误警报，然后才能合并拉取请求。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。 +如果 {% data variables.product.prodname_code_scanning %} 有任何严重性为 `error` 的结果，则检查失败，错误将报告在检查结果中。 如果 {% data variables.product.prodname_code_scanning %} 发现的所有结果的严重性都较低，则警报将被视为警告或通知，检查成功。 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 you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。 ![拉取请求上失败的 {% data variables.product.prodname_code_scanning %} 检查](/assets/images/help/repository/code-scanning-check-failure.png) diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md index 62c0bcbe59..1bbc0e86dc 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -24,7 +24,7 @@ versions: - 高 - 关键 -{% data variables.product.prodname_advisory_database %} 使用 CVSS 版本 3.0 标准和上述 CVSS 级别。 {% data variables.product.product_name %} 不发布 CVSS 分数。 +{% data variables.product.prodname_advisory_database %} 使用 CVSS 版本 3.0 标准和上述 CVSS 级别。 {% data reusables.repositories.github-security-lab %} @@ -41,24 +41,39 @@ versions: {% endnote %} ### 搜索 {% data variables.product.prodname_advisory_database %} -您可以搜索数据库，并使用限定符将搜索范围缩小到在特定日期、特定生态系统或特定库中创建的公告。 + +You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| 限定符 | 示例 | -| --------------------- | ----------------------------------------------------------------------------------------------------------------------- | -| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) 只显示影响 NPM 包的通告。 | -| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) 只显示严重程度高的公告。 | -| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) 只显示影响 lodash 库的通告。 | -| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) 按照时间顺序对通告排序，最早的通告排在最前面。 | -| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) 按照时间顺序对通告排序，最新的通告排在最前面。 | -| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) 按照更新顺序排序，最早更新的排在最前面。 | -| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) 按照更新顺序排序，最近更新的排在最前面。 | -| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) 只显示已经撤销的通告。 | -| `created:YYYY-MM-DD` | [**created:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2019-10-31) 只显示此日期创建的通告。 | -| `updated:YYYY-MM-DD` | [**updated:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2019-10-31) 只显示此日期更新的通告。 | +| 限定符 | 示例 | +| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `GHSA-ID` | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | +| `CVE-ID` | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | +| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) 只显示影响 NPM 包的通告。 | +| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) 只显示严重程度高的公告。 | +| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) 只显示影响 lodash 库的通告。 | +| `cwe:ID` | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | +| `credit:USERNAME` | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | +| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) 按照时间顺序对通告排序，最早的通告排在最前面。 | +| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) 按照时间顺序对通告排序，最新的通告排在最前面。 | +| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) 按照更新顺序排序，最早更新的排在最前面。 | +| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) 按照更新顺序排序，最近更新的排在最前面。 | +| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) 只显示已经撤销的通告。 | +| `created:YYYY-MM-DD` | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) 只显示此日期创建的通告。 | +| `updated:YYYY-MM-DD` | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) 只显示此日期更新的通告。 | + +### Viewing your vulnerable repositories + +For any vulnerability in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories have a {% data variables.product.prodname_dependabot %} alert for that vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)”。 + +1. 导航到 https://github.com/advisories。 +2. Click an advisory. +3. At the top of the advisory page, click **Dependabot alerts**. ![Dependabot 警报](/assets/images/help/security/advisory-database-dependabot-alerts.png) +4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) +5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name. ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index cd33442a3b..76fe3e1f07 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -12,6 +12,8 @@ versions: {% data reusables.github-actions.actions-spending-limit-brief %} 更多信息请参阅“[关于支出限制](#about-spending-limits)”。 +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 %} usage beyond the amounts including with your account. 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)." + 分钟数每月都会重置，而存储使用量不重置。 | 产品 | 存储器 | 分钟数（每月） | diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index a20304d0fa..c6450fe1c7 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.package_registry.container-registry-beta-billing-note %} +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_registry %} usage beyond the amounts including with your account. 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)." + 数据传输每月都会重置，而存储使用量不重置。 | 产品 | 存储器 | 数据传输（每月） | diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 44f9992b45..0722f66ecf 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} 有关 {% data variables.product.prodname_actions %} 使用价格的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)”。 +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 %} usage beyond the amounts including with your account. 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)." + 只要您将支出限额设定在 0 美元以上，您就要对当前结算周期内发生的任何超额费用负责。 例如，如果您的组织使用 {% data variables.product.prodname_team %}，不允许超额，并且创建将当月存储使用量从 1.9GB 增加到 2.1GB 的工作流程工件，那么您使用的存储空间将比产品包含的 2GB 稍高。 由于您尚未启用超额，因此下次尝试创建工作流程构件将失败。 您不会收到该月 0.1GB 超额费用的帐单。 但是，如果您启用了超额，您的第一个帐单将包括当前结算周期中 0.1GB 的现有超额以及您累积的任何其他超额。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index 008164e5f0..374b9c7d55 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -14,6 +14,8 @@ versions: {% data reusables.actions.actions-packages-set-spending-limit %} 有关 {% data variables.product.prodname_registry %} 使用价格的更多信息，请参阅“[关于 {% data variables.product.prodname_registry %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)”。 +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_registry %} usage beyond the amounts including with your account. 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)." + 只要您将支出限额设定在 0 美元以上，您就要对当前结算周期内发生的任何超额费用负责。 例如，如果您的组织使用 {% data variables.product.prodname_team %}，不允许超额，并且发布新版私有包，将当月存储使用量从 1.9GB 增加到 2.1GB，那么发布该版本使用的存储空间将比产品包含的 2GB 稍高。 由于您尚未启用超额，因此下次尝试发布包版本将失败。 您不会收到该月 0.1GB 超额费用的帐单。 但是，如果您启用了超额，您的第一个帐单将包括当前结算周期中 0.1GB 的现有超额以及您累积的任何其他超额。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 6f81953cad..4b442413dd 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -23,8 +23,13 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.security-and-analysis %} -显示的页面允许您为组织中的仓库启用或禁用所有安全和分析功能。 {% if currentVersion == "free-pro-team@latest" %}如果您的组织或拥有它的企业具有 {% data variables.product.prodname_GH_advanced_security %} 许可，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 +显示的页面允许您为组织中的仓库启用或禁用所有安全和分析功能。 +{% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has 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.{% endif %} + +{% if currentVersion ver_gt "enterprise-server@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.{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![{% data variables.product.prodname_GH_advanced_security %} 功能](/assets/images/help/organizations/security-and-analysis-highlight-ghas.png) {% endif %} @@ -42,24 +47,21 @@ versions: 1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。 1. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。 - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghe.png) {% endif %} 2. （可选）为组织中的新仓库默认启用该功能。 - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![新仓库的"Enable by default（默认启用）"选项](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![新仓库的"Enable by default（默认启用）"选项](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default-ghe.png) {% endif %} -1. 单击 **Disable FEATURE（禁用功能）**或 **Enable FEATURE（启用功能）**以禁用或启用组织中所有仓库的功能。 - {% if currentVersion == "free-pro-team@latest" %} +3. 单击 **Disable FEATURE（禁用功能）**或 **Enable FEATURE（启用功能）**以禁用或启用组织中所有仓库的功能。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![用于禁用或启用功能的按钮](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![用于禁用或启用功能的按钮](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning-ghe.png) {% endif %} @@ -68,10 +70,9 @@ versions: 1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。 1. 在功能右侧的“Configure security and analysis features（配置安全和分析功能）”下，默认对组织中的新仓库 {% if currentVersion == "free-pro-team@latest" %} 或所有新私有仓库{% endif %} 启用或禁用该功能。 - {% if currentVersion == "free-pro-team@latest" %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) - {% endif %} - {% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} + {% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %} ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghe.png) {% endif %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index f739d32bfd..df4a092ccb 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -70,7 +70,7 @@ versions: {% endif %} | 应用/忽略标签 | | **X** | **X** | **X** | **X** | | 创建、编辑、删除标签 | | | **X** | **X** | **X** | -| 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} | [在拉取请求上启用和禁用自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** {% endif %} | 应用里程碑 | | **X** | **X** | **X** | **X** | @@ -150,8 +150,8 @@ versions: | 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) | | | | | **X** | | [忽略 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | | [指定其他人员或团队接收易受攻击依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** | -| 创建[安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** | -| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** | +| 创建[安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | 为私有仓库[启用依赖关系图](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) | | | | | **X** | | [查看依赖项审查](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md new file mode 100644 index 0000000000..ea9b3d4b19 --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise.md @@ -0,0 +1,40 @@ +--- +title: Connecting an Azure subscription to your enterprise +intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the included amounts for your enterprise.' +product: '{% data reusables.gated-features.enterprise-accounts %}' +redirect_from: + - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise +versions: + free-pro-team: '*' +--- + +### About Azure subscriptions and {% data variables.product.product_name %} + +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 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) and "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." + +After you connect an Azure subscription, you can also manage your spending limit. For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)" and "[Managing your spending limit for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)." + +### Connecting your Azure subscription to your enterprise account + +To connect your Azure subscription, you must have owner permissions to the subscription. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Payment Information", click **Add Azure Subscription**. +1. To sign in to your Microsoft account, follow the prompts. +1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**. +1. Under "Select a subscription", select the Azure Subscription ID that you want to connect to your enterprise. +1. Click **Connect**. + +### Disconnecting your Azure subscription from your enterprise account + +After you disconnect your Azure subscription from your enterprise account, your usage can no longer exceed the amounts included with your plan. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.billing-tab %} +{% data reusables.enterprise-accounts.payment-information-tab %} +1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**. +1. Review the prompt, then click **Remove**. 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 99f6f505c2..93b712e993 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 @@ -18,6 +18,7 @@ versions: {% link_in_list /about-enterprise-accounts %} {% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %} {% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %} + {% link_in_list /connecting-an-azure-subscription-to-your-enterprise %} {% topic_link_in_list /managing-users-in-your-enterprise %} {% link_in_list /roles-in-an-enterprise %} {% link_in_list /inviting-people-to-manage-your-enterprise %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md index cb24a0fa1c..f3e6cd636b 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -15,6 +15,8 @@ versions: 企业帐户目前适用于通过发票付费的 {% data variables.product.prodname_enterprise %} 客户。 对与企业帐户关联的所有组织和 {% data variables.product.prodname_ghe_server %} 实例的结算将汇总为所有付费 {% data variables.product.prodname_dotcom_the_website %} 服务（包括组织中的付费许可、{% data variables.large_files.product_name_long %} 数据包和 {% data variables.product.prodname_marketplace %} 应用程序的订阅）的单一帐单费用。 +{% if currentVersion == "free-pro-team@latest" %}{% 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)."{% endif %} + 有关管理帐单管理员的更多信息，请参阅“[邀请人员管理企业](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)”。 ### 查看企业帐户的订阅和使用情况 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md index 448b934644..63b65063f1 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository.md @@ -25,32 +25,32 @@ versions: 仓库所有者对仓库具有完全控制权。 除了任何协作者可以执行的操作外，仓库所有者还可以执行以下操作。 -| 操作 | 更多信息 | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% if currentVersion == "free-pro-team@latest" %}邀请协作者{% else %}添加协作者{% endif %} | | -| "[邀请个人仓库的协作者](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | +| 操作 | 更多信息 | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% if currentVersion == "free-pro-team@latest" %}邀请协作者{% else %}添加协作者{% endif %} | | +| "[邀请个人仓库的协作者](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | | 更改仓库的可见性 | “[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)” |{% if currentVersion == "free-pro-team@latest" %} | 限制与仓库的交互 | "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} | 重命名分支，包括默认分支 | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" {% endif %} -| 合并受保护分支上的拉取请求（即使没有批准审查） | "[关于受保护分支](/github/administering-a-repository/about-protected-branches)" | -| 删除仓库 | "[删除仓库](/github/administering-a-repository/deleting-a-repository)" | +| 合并受保护分支上的拉取请求（即使没有批准审查） | "[关于受保护分支](/github/administering-a-repository/about-protected-branches)" | +| 删除仓库 | "[删除仓库](/github/administering-a-repository/deleting-a-repository)" | | 管理仓库的主题 | "[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% if currentVersion == "free-pro-team@latest" %} | 管理仓库的安全性和分析设置 | "[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | 为私有仓库启用依赖项图 | “[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)” |{% endif %}{% if currentVersion == "free-pro-team@latest" %} | 删除包 | “[删除包](/github/managing-packages-with-github-packages/deleting-a-package)” {% endif %} -| 自定义仓库的社交媒体预览 | "[自定义仓库的社交媒体预览](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | +| 自定义仓库的社交媒体预览 | "[自定义仓库的社交媒体预览](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | | 从仓库创建模板 | "[创建模板仓库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -| 接收 | | +| 接收 | | | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}有漏洞依赖项{% data variables.product.prodname_dependabot_alerts %}{% else %}安全警报{% endif %} | "[关于有漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| 忽略仓库中的 {% data variables.product.prodname_dependabot_alerts %} | "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | +| 忽略仓库中的 {% data variables.product.prodname_dependabot_alerts %} | "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | | 管理私有仓库的数据使用 | “[管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)” {% endif %} -| 定义仓库的代码所有者 | "[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | +| 定义仓库的代码所有者 | "[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | | 存档仓库 | "[关于存档仓库](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %} -| 创建安全通告 | "[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | -| 显示赞助按钮 | “[在仓库中显示赞助按钮](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)” | +| 创建安全通告 | "[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | +| 显示赞助按钮 | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} | 允许或禁止自动合并拉取请求 | "[管理仓库中的拉取请求自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %} ### 协作者对用户帐户拥有仓库的权限 diff --git a/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md b/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md index 92085b6c2d..36b4e58c47 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md +++ b/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll.md @@ -25,8 +25,6 @@ versions: {% 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 %} @@ -36,6 +34,8 @@ versions: {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% data reusables.command_line.open_the_multi_os_terminal %} 2. 如果您还没有本地版仓库，请导航到您想要存储站点源文件的位置，将 _PARENT-FOLDER_ 替换为要包含仓库文件夹的文件夹。 ```shell diff --git a/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site.md b/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site.md index 3e403e8f01..fa5fdd1fb6 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site.md +++ b/translations/zh-CN/content/github/working-with-github-pages/creating-a-github-pages-site.md @@ -20,8 +20,6 @@ versions: {% 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 %} @@ -33,6 +31,8 @@ versions: {% data reusables.pages.must-have-repo-first %} +{% data reusables.pages.private_pages_are_public_warning %} + {% data reusables.pages.navigate-site-repo %} {% data reusables.pages.decide-publishing-source %} 3. 如果所选发布源已存在，请导航到发布源。 如果所选发布源不存在，则创建发布源。 diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md index f5029067e6..2c64f6bf41 100644 --- a/translations/zh-CN/content/rest/overview/libraries.md +++ b/translations/zh-CN/content/rest/overview/libraries.md @@ -57,7 +57,7 @@ Library name | Repository | |---|---| **NodeJS GitHub library**| [pksunkara/octo ### Julia -Library name | Repository | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl) +Library name | Repository | |---|---| **GitHub.jl**|[WestleyArgentum/GitHub.jl](https://github.com/WestleyArgentum/GitHub.jl) ### OCaml @@ -65,11 +65,11 @@ Library name | Repository | |---|---| **ocaml-github**|[mirage/ocaml-github](htt ### Perl -Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub) +Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub) ### PHP -Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI) +Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GitHubAPI](https://github.com/FlexyProject/GitHubAPI) ### Python diff --git a/translations/zh-CN/content/rest/reference/pulls.md b/translations/zh-CN/content/rest/reference/pulls.md index ccebc90c9f..56ca1a2591 100644 --- a/translations/zh-CN/content/rest/reference/pulls.md +++ b/translations/zh-CN/content/rest/reference/pulls.md @@ -42,7 +42,7 @@ versions: | `review_comments` | 此拉取请求的[审查评论](/rest/reference/pulls#comments)的 API 位置。 | | `review_comment` | 用于为此拉取请求仓库中的[审查评论](/rest/reference/pulls#comments)构建 API 位置的 [URL 模板](/rest#hypermedia)。 | | `commits` | 此拉取请求的[提交](#list-commits-on-a-pull-request)的 API 位置。 | -| `statuses` | 此拉取请求的[提交状态](/rest/reference/repos#statuses)的 API 位置，即其`头部`分支的状态。 | +| `状态` | 此拉取请求的[提交状态](/rest/reference/repos#statuses)的 API 位置，即其`头部`分支的状态。 | {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} diff --git a/translations/zh-CN/content/rest/reference/repos.md b/translations/zh-CN/content/rest/reference/repos.md index fa306aeed9..2d12e86773 100644 --- a/translations/zh-CN/content/rest/reference/repos.md +++ b/translations/zh-CN/content/rest/reference/repos.md @@ -141,7 +141,7 @@ versions: ### 非活动部署 -当您将部署状态设置为 `success` 时，同一仓库中所有先前的非瞬态、非生产环境部署将变成 `inactive`。 为避免这种情况，您可以在创建部署状态时将 `auto_inactive` 设置为 `false`。 +When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository to the same environment name will become `inactive`. 为避免这种情况，您可以在创建部署状态时将 `auto_inactive` 设置为 `false`。 您可以通过将 `state` 设为 `inactive` 来表示某个瞬态环境不再存在。 将 `state` 设为 `inactive`，表示部署在 {% data variables.product.prodname_dotcom %} 中 `destroyed` 并删除对它的访问权限。 diff --git a/translations/zh-CN/data/reusables/actions/enterprise-beta.md b/translations/zh-CN/data/reusables/actions/enterprise-beta.md index ef497fcaf4..0c674122af 100644 --- a/translations/zh-CN/data/reusables/actions/enterprise-beta.md +++ b/translations/zh-CN/data/reusables/actions/enterprise-beta.md @@ -1,7 +1,12 @@ {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %} {% note %} -**注：**{% data variables.product.prodname_ghe_server %} 2.22 上的 {% 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)”。 +**Note:** {% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. The beta has ended. {% data variables.product.prodname_actions %} is now generally available in {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes). + +
+ +- For more information about upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." +- For more information about configuring {% data variables.product.prodname_actions %} after you upgrade, see the [documentation for {% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server). {% endnote %} {% endif %} diff --git a/translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md b/translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md index 0856d5e583..72e20d349d 100644 --- a/translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md +++ b/translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md @@ -1,4 +1,4 @@ -* {% data reusables.actions.enterprise-hardware-considerations %} +* Review the hardware requirements for {% data variables.product.prodname_actions %}. 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#review-hardware-considerations)." * TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." {% note %} diff --git a/translations/zh-CN/data/reusables/actions/enterprise-hardware-considerations.md b/translations/zh-CN/data/reusables/actions/enterprise-hardware-considerations.md index 24c077bbae..98ac65f438 100644 --- a/translations/zh-CN/data/reusables/actions/enterprise-hardware-considerations.md +++ b/translations/zh-CN/data/reusables/actions/enterprise-hardware-considerations.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "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)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}. +If you {% if currentVersion == "enterprise-server@2.22" %} configured the beta of{% else %} configure{% endif %} {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, we recommend that you provision additional CPU and memory resources. The additional resources you need to provision depend on the number of workflows your users run concurrently, and the overall levels of activity for your instance. diff --git a/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md index 48f3c5a99a..733e8e8a97 100644 --- a/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md +++ b/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -1,7 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} {% note %} -**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. +**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. This option controls access to all {% data variables.product.prodname_advanced_security %} features including {% if currentVersion == "free-pro-team@latest" %}dependency review,{% endif %} {% data variables.product.prodname_code_scanning %}, and {% data variables.product.prodname_secret_scanning %}. {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/code-scanning/enabling-options.md b/translations/zh-CN/data/reusables/code-scanning/enabling-options.md index 92f3fc578d..43c7e9c2fc 100644 --- a/translations/zh-CN/data/reusables/code-scanning/enabling-options.md +++ b/translations/zh-CN/data/reusables/code-scanning/enabling-options.md @@ -15,7 +15,7 @@ - 使用 {% data variables.product.prodname_actions %}（请参阅“使用操作启用 {% data variables.product.prodname_code_scanning %}”）或在第三方持续集成 (CI) 系统中使用 {% data variables.product.prodname_codeql_runner %}（请参阅“在 CI 系统中运行代码扫描”）。 + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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"). @@ -25,7 +25,7 @@ - 使用 {% data variables.product.prodname_actions %}（请参阅“使用操作启用 {% data variables.product.prodname_code_scanning %}”）或者外部生成并上传到 {% data variables.product.product_name %}（请参阅“上传 SARIF 文件到 {% data variables.product.prodname_dotcom %}”）。 + Using {% data variables.product.prodname_actions %} (see "Setting up {% 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 %}"). 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 b2a7c4d273..61d16f8d42 100644 --- a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md +++ b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md @@ -1,35 +1,35 @@ -The following table shows, for each package manager: -- The YAML value to use in the *dependabot.yml* file -- The supported versions of the package manager -- Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories are supported -- Whether vendored dependencies are supported +下表对每个包管理器显示： +- 要用于 *dependabot.yml* 文件中的 YAML 值 +- 支持的包管理器版本 +- 是否支持私有 {% data variables.product.prodname_dotcom %} 仓库中的依赖项 +- 是否支持供应的依赖项 -| 包管理器 | YAML value | Supported versions | Private repositories | 供应 | -| -------------- | ---------------- | ------------------------- |:--------------------:|:-----:| -| Bundler | `bundler` | v1 | | **✓** | -| Cargo | `cargo` | v1 | **✓** | | -| Composer | `composer` | v1,v2 | **✓** | | -| Docker | `docker` | v1 | **✓** | | -| Elixir | `mix` | v1 | **✓** | | -| Elm | `elm` | v0.18, v0.19 | **✓** | | -| git submodule | `gitsubmodule` | N/A (no version) | **✓** | | -| GitHub Actions | `github-actions` | N/A (no version) | **✓** | | -| Go modules | `gomod` | v1 | **✓** | **✓** | -| Gradle | `gradle` | see (A) below | **✓** | | -| Maven | `maven` | see (B) below | **✓** | | -| npm | `npm` | v6 | **✓** | | -| NuGet | `nuget` | <= 4.8.
see (C) below | **✓** | | -| pip | `pip` | v20 | | | -| pipenv | `pip` | <= 2018.11.26 | | | -| pip-compile | `pip` | 5.5.0 | | | -| poetry | `pip` | v1 | | | -| Terraform | `terraform` | <= 0.11 | **✓** | | -| yarn | `npm` | v1 | | | +| 包管理器 | YAML 值 | 支持的版本 | 私有仓库 | 供应 | +| -------------- | ---------------- | --------------------- |:-----:|:-----:| +| Bundler | `bundler` | v1 | | **✓** | +| Cargo | `cargo` | v1 | **✓** | | +| Composer | `composer` | v1, v2 | **✓** | | +| Docker | `docker` | v1 | **✓** | | +| Elixir | `混合` | v1 | **✓** | | +| Elm | `elm` | v0.18, v0.19 | **✓** | | +| git submodule | `gitsubmodule` | N/A（无版本） | **✓** | | +| GitHub Actions | `github-actions` | N/A（无版本） | **✓** | | +| Go 模块 | `gomod` | v1 | **✓** | **✓** | +| Gradle | `gradle` | 参阅 (A) 下文 | **✓** | | +| Maven | `maven` | 参阅 (B) 下文 | **✓** | | +| npm | `npm` | v6, v7 | **✓** | | +| NuGet | `nuget` | <= 4.8.
参阅 (C) 下文 | **✓** | | +| pip | `pip` | v20 | | | +| pipenv | `pip` | <= 2018.11.26 | | | +| pip-compile | `pip` | 5.5.0 | | | +| poetry | `pip` | v1 | | | +| Terraform | `terraform` | <= 0.11 | **✓** | | +| yarn | `npm` | v1 | | | -(A) {% 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). +(A) {% data variables.product.prodname_dependabot %} 不运行 Gradle，但支持更新以下文件：`build.gradle` 和 `build.gradle.kts`（用于 Kotlin 项目）。 -(B) {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. +(B) {% data variables.product.prodname_dependabot %} 不运行 Maven ，但支持更新 `pom.xml` 文件。 -(C) {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8. +(C) {% data variables.product.prodname_dependabot %} 不运行 NuGet CLI，但支持直到版本 4.8 的大多数功能。 -For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. 例如，如果您使用 `poetry` 来管理 Python 依赖项，并且希望 {% data variables.product.prodname_dependabot %} 监控新版本的依赖项清单文件，请在 *dependabot.yml* 文件中使用 `package-ecosystem: "pip"`。 +对于包管理器，如 `pipenv` 和 `poetry`，您需要使用 `pip` YAML 值。 例如，如果您使用 `poetry` 来管理 Python 依赖项，并且希望 {% data variables.product.prodname_dependabot %} 监控新版本的依赖项清单文件，请在 *dependabot.yml* 文件中使用 `package-ecosystem: "pip"`。 diff --git a/translations/zh-CN/data/reusables/desktop/choose-clone-repository.md b/translations/zh-CN/data/reusables/desktop/choose-clone-repository.md index e82def1d5f..fa411bd606 100644 --- a/translations/zh-CN/data/reusables/desktop/choose-clone-repository.md +++ b/translations/zh-CN/data/reusables/desktop/choose-clone-repository.md @@ -1 +1,13 @@ 1. 在 **File（文件）**菜单中，单击 **Clone Repository（克隆仓库）**。 + + {% mac %} + + ![Mac 应用程序中的克隆菜单选项](/assets/images/help/desktop/clone-file-menu-mac.png) + + {% endmac %} + + {% windows %} + + ![Windows 应用程序中的克隆菜单选项](/assets/images/help/desktop/clone-file-menu-windows.png) + + {% endwindows %} diff --git a/translations/zh-CN/data/reusables/desktop/choose-local-path.md b/translations/zh-CN/data/reusables/desktop/choose-local-path.md new file mode 100644 index 0000000000..4e9c84df66 --- /dev/null +++ b/translations/zh-CN/data/reusables/desktop/choose-local-path.md @@ -0,0 +1,13 @@ +1. Click **Choose...** and navigate to a local path where you want to clone the repository. + + {% mac %} + + ![选择按钮](/assets/images/help/desktop/clone-choose-button-mac.png) + + {% endmac %} + + {% windows %} + + ![选择按钮](/assets/images/help/desktop/clone-choose-button-win.png) + + {% endwindows %} diff --git a/translations/zh-CN/data/reusables/desktop/click-clone.md b/translations/zh-CN/data/reusables/desktop/click-clone.md new file mode 100644 index 0000000000..ff0f9cd2cc --- /dev/null +++ b/translations/zh-CN/data/reusables/desktop/click-clone.md @@ -0,0 +1,14 @@ +1. 单击 **Clone（克隆）**。 + + {% mac %} + + ![克隆按钮](/assets/images/help/desktop/clone-button-mac.png) + + {% endmac %} + + {% windows %} + + ![克隆按钮](/assets/images/help/desktop/clone-button-win.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/desktop/cloning-location-tab.md b/translations/zh-CN/data/reusables/desktop/cloning-location-tab.md index 6abb1dc137..9f68442c24 100644 --- a/translations/zh-CN/data/reusables/desktop/cloning-location-tab.md +++ b/translations/zh-CN/data/reusables/desktop/cloning-location-tab.md @@ -1 +1,13 @@ 1. 单击与要克隆的仓库位置对应的选项卡。 您也可以单击 **URL** 手动输入仓库位置。 + + {% mac %} + + ![克隆仓库菜单中的 Location（位置）选项卡](/assets/images/help/desktop/choose-repository-location-mac.png) + + {% endmac %} + + {% windows %} + + ![克隆仓库菜单中的 Location（位置）选项卡](/assets/images/help/desktop/choose-repository-location-win.png) + + {% endwindows %} diff --git a/translations/zh-CN/data/reusables/desktop/cloning-repository-list.md b/translations/zh-CN/data/reusables/desktop/cloning-repository-list.md index f0bf43f0b1..2504fb3638 100644 --- a/translations/zh-CN/data/reusables/desktop/cloning-repository-list.md +++ b/translations/zh-CN/data/reusables/desktop/cloning-repository-list.md @@ -1 +1,14 @@ 1. 从列表中选择要克隆的仓库。 + + + {% mac %} + + ![克隆仓库列表](/assets/images/help/desktop/clone-a-repository-list-mac.png) + + {% endmac %} + + {% windows %} + + ![克隆仓库列表](/assets/images/help/desktop/clone-a-repository-list-win.png) + + {% endwindows %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/desktop/fork-type-prompt.md b/translations/zh-CN/data/reusables/desktop/fork-type-prompt.md new file mode 100644 index 0000000000..1067dab748 --- /dev/null +++ b/translations/zh-CN/data/reusables/desktop/fork-type-prompt.md @@ -0,0 +1,42 @@ +1. If you plan to use this fork for contributing to the original upstream repository, click **To contribute to the parent project**. + + {% mac %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/mac-fork-options-prompt.png) + + {% endmac %} + + {% windows %} + + ![Contribute to the parent project menu option](/assets/images/help/desktop/windows-fork-options-prompt.png) + + {% endwindows %} + +2. If you plan to use this fork for a project not connected to the upstream, click **For my own purposes**. + + {% mac %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/mac-fork-own-purposes.png) + + {% endmac %} + + {% windows %} + + ![Contribute to an independent project menu option](/assets/images/help/desktop/windows-fork-own-purposes.png) + + {% endwindows %} + +3. Click **Continue**. + + {% mac %} + + ![The continue button](/assets/images/help/desktop/mac-forking-continue.png) + + {% endmac %} + + {% windows %} + + ![The continue button](/assets/images/help/desktop/windows-forking-continue.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/desktop/open-repository-settings.md b/translations/zh-CN/data/reusables/desktop/open-repository-settings.md new file mode 100644 index 0000000000..5e298edc85 --- /dev/null +++ b/translations/zh-CN/data/reusables/desktop/open-repository-settings.md @@ -0,0 +1,14 @@ +1. Open the **Repository** menu, then click **Repository settings...**. + + {% mac %} + + ![Repository settings menu option in the Mac app](/assets/images/help/desktop/mac-repository-settings.png) + + {% endmac %} + + {% windows %} + + ![Repository settings menu option in the Windows app](/assets/images/help/desktop/windows-repository-settings.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/desktop/select-fork-behavior.md b/translations/zh-CN/data/reusables/desktop/select-fork-behavior.md new file mode 100644 index 0000000000..1225972873 --- /dev/null +++ b/translations/zh-CN/data/reusables/desktop/select-fork-behavior.md @@ -0,0 +1,28 @@ +1. Click **Fork behavior**, then select how you want to use the fork. + + {% mac %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-menu-contribute.png) + + {% endmac %} + + {% windows %} + + ![The contribute to the parent repository option in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-menu-contribute.png) + + {% endwindows %} + +2. 单击 **Save（保存）**。 + + {% mac %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/mac-fork-behavior-save.png) + + {% endmac %} + + {% windows %} + + ![The save button in the Fork Behavior menu](/assets/images/help/desktop/windows-fork-behavior-save.png) + + {% endwindows %} + \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md b/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md index a17ca2ca53..76f8fc5557 100644 --- a/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md +++ b/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md @@ -1 +1 @@ -All discussions must be created in a category, and repository administrators and maintainers define the categories for a repository. Categories can contain open-ended conversations, or conversations with a question/answer format. +所有讨论必须在一个类别中创建，仓库管理员和维护员定义仓库的类别。 类别可以包含开放式对话，也可以包含问题/回答格式的对话。 diff --git a/translations/zh-CN/data/reusables/discussions/click-discussion-in-list.md b/translations/zh-CN/data/reusables/discussions/click-discussion-in-list.md index 1fc74494be..6c64e4a353 100644 --- a/translations/zh-CN/data/reusables/discussions/click-discussion-in-list.md +++ b/translations/zh-CN/data/reusables/discussions/click-discussion-in-list.md @@ -1 +1 @@ -1. 在讨论列表中，单击要查看的讨论。 ![Discussion in list of discussions for a repository](/assets/images/help/discussions/click-discussion-in-list.png) +1. 在讨论列表中，单击要查看的讨论。 ![仓库讨论列表中的讨论](/assets/images/help/discussions/click-discussion-in-list.png) diff --git a/translations/zh-CN/data/reusables/discussions/github-recognizes-members.md b/translations/zh-CN/data/reusables/discussions/github-recognizes-members.md index b6874b910d..4341daa780 100644 --- a/translations/zh-CN/data/reusables/discussions/github-recognizes-members.md +++ b/translations/zh-CN/data/reusables/discussions/github-recognizes-members.md @@ -1 +1 @@ -{% data variables.product.prodname_dotcom %} will automatically recognize community members who contribute the most comments marked as answers to discussions with a question/answer format. +{% data variables.product.prodname_dotcom %} 将自动识别贡献最多评论的社区成员，将评论标记为问题/回答格式的讨论答案。 diff --git a/translations/zh-CN/data/reusables/discussions/you-can-categorize-discussions.md b/translations/zh-CN/data/reusables/discussions/you-can-categorize-discussions.md index bb05316d77..7e70f7a49e 100644 --- a/translations/zh-CN/data/reusables/discussions/you-can-categorize-discussions.md +++ b/translations/zh-CN/data/reusables/discussions/you-can-categorize-discussions.md @@ -1 +1 @@ -You can categorize discussions to help community members begin conversations in the right place, and to help community members find related discussions. +您可以对讨论进行分类，以帮助社区成员在正确的位置开始对话，并帮助社区成员查找相关的讨论。 diff --git a/translations/zh-CN/data/reusables/discussions/you-can-convert-an-issue.md b/translations/zh-CN/data/reusables/discussions/you-can-convert-an-issue.md index 1421256e1f..54d2e78ae0 100644 --- a/translations/zh-CN/data/reusables/discussions/you-can-convert-an-issue.md +++ b/translations/zh-CN/data/reusables/discussions/you-can-convert-an-issue.md @@ -1 +1 @@ -If an issue turns out to be a question or open-ended conversation instead of a work item to track and prioritize, you can convert the issue to a discussion. +如果议题原来是问题或开放式对话，而不是要跟踪和确定优先级的工作项，则您可以将议题转换为讨论。 diff --git a/translations/zh-CN/data/reusables/discussions/you-can-use-discussions.md b/translations/zh-CN/data/reusables/discussions/you-can-use-discussions.md index 27c1ba7cb2..bfc49add3e 100644 --- a/translations/zh-CN/data/reusables/discussions/you-can-use-discussions.md +++ b/translations/zh-CN/data/reusables/discussions/you-can-use-discussions.md @@ -1 +1 @@ -You can use discussions to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." \ No newline at end of file +您可以使用讨论来提问和回答问题、共享信息、发布公告以及进行或参与有关项目的对话。 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md b/translations/zh-CN/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md new file mode 100644 index 0000000000..63fa9473e7 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md @@ -0,0 +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 including with your account. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md b/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md index 1c21b4eb95..6f35bb03df 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-administrators.md @@ -1 +1 @@ -{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}目前，企业帐户中有两个管理角色：企业所有者，可以访问和管理帐户中所有设置；帐单管理员，只能访问和管理企业帐户的帐单设置。 {% endif %}企业所有者{% if enterpriseServersions contains currentversion or currentversion == "free promo-team@latest" %}还{% endif %}能查看企业拥有的每个组织的所有成员和外部协作者。 +{% if enterpriseServerVersions contains currentVersion or currentVersion == "free-pro-team@latest" %}目前，企业帐户中有两个管理角色：企业所有者，可以访问和管理帐户中所有设置；帐单管理员，只能访问和管理企业帐户的帐单设置。 {% endif %}企业所有者{% if enterpriseServersions contained currentversion or currentversion == "free promo-team@latest" %}还{% endif %}能查看企业拥有的每个组织的所有成员和外部协作者。 diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/payment-information-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/payment-information-tab.md new file mode 100644 index 0000000000..4de0966ad7 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/payment-information-tab.md @@ -0,0 +1 @@ +1. Under "Billing", click **Payment information**. diff --git a/translations/zh-CN/data/reusables/enterprise_installation/about-adjusting-resources.md b/translations/zh-CN/data/reusables/enterprise_installation/about-adjusting-resources.md new file mode 100644 index 0000000000..a00f883e61 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise_installation/about-adjusting-resources.md @@ -0,0 +1 @@ +有关为现有实例调整资源的更多信息，请参阅“[增加存储容量](/enterprise/admin/installation/increasing-storage-capacity)”和“[增加 CPU 或内存资源](/enterprise/admin/installation/increasing-cpu-or-memory-resources)”。 diff --git a/translations/zh-CN/data/reusables/enterprise_installation/aws-supported-instance-types.md b/translations/zh-CN/data/reusables/enterprise_installation/aws-supported-instance-types.md index c742114644..e0354fdd40 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/aws-supported-instance-types.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/aws-supported-instance-types.md @@ -1,37 +1,13 @@ -以下类型的 EC2 实例支持 {% data variables.product.prodname_ghe_server %}。 更多信息请参阅 [the AWS EC2 实例类型概述页面](http://aws.amazon.com/ec2/instance-types/)。 +{% data variables.product.prodname_ghe_server %} is supported on the following EC2 instance sizes. 更多信息请参阅 [the AWS EC2 实例类型概述页面](http://aws.amazon.com/ec2/instance-types/)。 -| EC2 实例类型 | 模型 | -| -------- | -------------------------------- | -| C3 | c3.2xlarge、c3.4xlarge、c3.8xlarge | - -| EC2 实例类型 | 模型 | -| -------- | -------------------------------- | -| C4 | c4.2xlarge、c4.4xlarge、c4.8xlarge | - -| EC2 实例类型 | 模型 | -| -------- | --------------------------------------------------------------- | -| C5 | c5.large、c5.xlarge、c5.2xlarge、c5.4xlarge、c5.9xlarge、c5.18xlarge | - -| EC2 实例类型 | 模型 | -| -------- | -------------------- | -| M3 | m3.xlarge、m3.2xlarge | - -| EC2 实例类型 | 模型 | -| -------- | ------------------------------------------------------- | -| M4 | m4.xlarge、m4.2xlarge、m4.4xlarge、m4.10xlarge、m4.16xlarge | - -| EC2 实例类型 | 模型 | -| -------- | ---------------------------------------------------------------- | -| M5 | m5.large、m5.xlarge、m5.2xlarge、m5.4xlarge、m5.12xlarge、m5.24xlarge | - -| EC2 实例类型 | 模型 | -| -------- | --------------------------------------------------------------- | -| R4 | r4.large、r4.xlarge、r4.2xlarge、r4.4xlarge、r4.8xlarge、r4.16xlarge | - -| EC2 实例类型 | 模型 | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} - -| EC2 实例类型 | 模型 | -| -------- | ----------------------- | -| X1 | x1.16xlarge、x1.32xlarge | +| 类型 | Size | +|:-- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| C3 | c3.2xlarge、c3.4xlarge、c3.8xlarge | +| C4 | c4.2xlarge、c4.4xlarge、c4.8xlarge | +| C5 | c5.large、c5.xlarge、c5.2xlarge、c5.4xlarge、c5.9xlarge、c5.18xlarge | +| M3 | m3.xlarge、m3.2xlarge | +| M4 | m4.xlarge、m4.2xlarge、m4.4xlarge、m4.10xlarge、m4.16xlarge | +| M5 | m5.large、m5.xlarge、m5.2xlarge、m5.4xlarge、m5.12xlarge、m5.24xlarge | +| R4 | r4.large、r4.xlarge、r4.2xlarge、r4.4xlarge、r4.8xlarge、r4.16xlarge | +| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %} +| X1 | x1.16xlarge、x1.32xlarge | diff --git a/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md index c4d45fc7ce..86c53d018c 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md @@ -1,6 +1,5 @@ - [最低要求](#minimum-requirements){% if currentversion == "enterprise-server@2.22" %} -- [ {% data variables.product.prodname_ghe_server %} 2.22 的测试版功能](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentversion ver_gt "enterprise-server@2.22" %} -- [可选功能](#optional-features){% endif %} +- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %} - [存储器](#storage) - [CPU 和内存](#cpu-and-memory) @@ -8,20 +7,7 @@ 建议根据 {% data variables.product.product_location %} 的用户许可数选择不同的硬件配置。 如果预配的资源超过最低要求，您的实例将表现出更好的性能和扩展。 -{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} 如果您对 {% endif %}{% data variables.product.prodname_actions %} 启用 {% if currentVersion == "enterprise-server@2.22" %}测试版，请查看以下要求和建议。 - -- 您必须为 {% data variables.product.prodname_actions %} 工作流程配置至少一个运行器。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”。 -- 您必须配置外部 Blob 存储。 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)." -- 您可能需要配置额外的 CPU 和内存资源。 需要为 {% data variables.product.prodname_actions %} 预配的额外 CPU 和内存资源取决于用户同时运行的工作流程数量，以及用户活动、自动化和集成的总体水平。 - - | 每分钟最大作业数 | 额外的 vCPU | 额外内存 | - |:-------- | --------:| -------:| - | 轻型测试 | 4 | 30.5 GB | - | 25 | 8 | 61 GB | - | 35 | 16 | 122 GB | - | 100 | 32 | 244 GB | - -{% endif %} +{% data reusables.enterprise_installation.hardware-rec-table %} #### 存储器 @@ -31,7 +17,7 @@ {% if currentVersion ver_gt "enterprise-server@2.21" %} -如果启用{% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %}测试版{% endif %}，则需要配置外部 Blob 存储。 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)." +To configure{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you must provide external blob storage. 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)." {% endif %} @@ -39,7 +25,7 @@ #### CPU 和内存 -{% data variables.product.prodname_ghe_server %} 需要更多的 CPU 和内存资源，取决于用户活动、自动化和集成的水平。 +The CPU and memory resources that {% data variables.product.prodname_ghe_server %} requires depend on the levels of activity for users, automations, and integrations. {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data reusables.actions.enterprise-hardware-considerations %}{% endif %} {% data reusables.enterprise_installation.increasing-cpus-req %} diff --git a/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md index 6ab51e8163..b1fd1d3465 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md @@ -1,20 +1,20 @@ -{% if currentVersion ver_gt "enterprise-server@2.21" %} +{% if currentVersion == "enterprise-server@2.22" %} {% note %} -**注**：如果您在 {% data variables.product.prodname_actions %} 或 {% data variables.product.prodname_registry %} 中启用测试功能，则您的实例需要额外的硬件资源。 {% if currentVersion == "enterprise-server@2.22" %}测试{% else %}可选{% endif %}功能启用的实例的最低要求在下表中**加粗**。 更多信息请参阅“{% if currentVersion == "enterprise-server@2.22" %}[{% data variables.product.prodname_ghe_server %} 2.22 中的测试功能](#beta-features-in-github-enterprise-server-222){% else %}[可选功能](#optional-features){% endif %}”。 +**Note**: If you joined the beta for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} and enabled the features, your instance requires additional hardware resources. 启用测试功能的实例的最低要求在下表中用**粗体**表示。 更多信息请参阅“[{% data variables.product.prodname_ghe_server %} 2.22 中的测试功能](#beta-features-in-github-enterprise-server-222)”。 {% endnote %} {% endif %} {% if currentVersion ver_gt "enterprise-server@2.22" %} -| 用户许可 | vCPU | 内存 | 附加的存储容量 | 根存储容量 | -|:----------------- | -------------------------------------------:| ---------------------------------------------------:| ---------------------------------------------------:| ------:| -| 试用版、演示版或 10 个轻度用户 | 2
或 [**4**](#optional-features) | 16 GB
或 [**32 GB**](#optional-features) | 100 GB
或 [**150 GB**](#optional-features) | 200 GB | -| 10-3000 | 4
或 [**8**](#optional-features) | 32 GB
或 [**48 GB**](#optional-features) | 250 GB
或 [**300 GB**](#optional-features) | 200 GB | -| 3000-5000 | 8
或 [**12**](#optional-features) | 64 GB | 500 GB | 200 GB | -| 5000-8000 | 12
或 [**16**](#optional-features) | 96 GB | 750 GB | 200 GB | -| 8000-10000+ | 16
或 [**20**](#optional-features) | 128 GB
或 [**160 GB**](#optional-features) | 1000 GB | 200 GB | +| 用户许可 | vCPU | 内存 | 附加的存储容量 | 根存储容量 | +|:----------------- | ----:| ------:| -------:| ------:| +| 试用版、演示版或 10 个轻度用户 | 4 | 32 GB | 150 GB | 200 GB | +| 10-3000 | 8 | 48 GB | 300 GB | 200 GB | +| 3000-5000 | 12 | 64 GB | 500 GB | 200 GB | +| 5000-8000 | 16 | 96 GB | 750 GB | 200 GB | +| 8000-10000+ | 20 | 160 GB | 1000 GB | 200 GB | {% else %} @@ -28,22 +28,20 @@ {% endif %} -有关为现有实例调整资源的更多信息，请参阅“[增加存储容量](/enterprise/admin/installation/increasing-storage-capacity)”和“[增加 CPU 或内存资源](/enterprise/admin/installation/increasing-cpu-or-memory-resources)”。 +{% data reusables.enterprise_installation.about-adjusting-resources %} + +{% if currentVersion ver_gt "enterprise-server@2.22" %} + +If you plan to configure {% data variables.product.prodname_actions %} for your instance, you should provision additional resources. You must also configure at least one self-hosted runner to execute workflows. 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)." + +{% endif %} {% if currentVersion == "enterprise-server@2.22" %} #### {% data variables.product.prodname_ghe_server %} 2.22 中的测试功能 -您可以注册 {% data variables.product.prodname_ghe_server %} 2.22 中可用的试用功能，例如 {% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_code_scanning %}。 更多信息请参阅 {% data variables.product.prodname_enterprise %} 网站上的 [2.22 系列发行说明](https://enterprise.github.com/releases/series/2.22#release-2.22.0)。 +{% data variables.product.prodname_ghe_server %} 2.22 offered features in beta, such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [{% data variables.product.prodname_ghe_server %} 2.22 release notes](/enterprise-server@2.22/admin/release-notes#2.22.0). -如果您为 {% data variables.product.prodname_ghe_server %} 2.22 启用测试功能，则您的实例需要额外的硬件资源。 更多信息请参阅“[最低要求](#minimum-requirements)”。 - -{% elsif currentVersion ver_gt "enterprise-server@2.22" %} - -#### 可选功能 - -您可以启用 {% data variables.product.prodname_ghe_server %} 的可选功能，如 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %}。 更多信息请参阅“[对 {% data variables.product.prodname_ghe_server %} 开始使用 {% data variables.product.prodname_actions %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)”或“[对企业开始使用 {% data variables.product.prodname_registry %}](/admin/packages/getting-started-with-github-packages-for-your-enterprise)”。 - -如果启用可选功能，则实例需要额外的硬件资源。 更多信息请参阅“[最低要求](#minimum-requirements)”。 +If you enabled beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. 更多信息请参阅“[最低要求](#minimum-requirements)”。 {% endif %} diff --git a/translations/zh-CN/data/reusables/gated-features/auto-merge.md b/translations/zh-CN/data/reusables/gated-features/auto-merge.md index 72a58ba07d..acfb4dddff 100644 --- a/translations/zh-CN/data/reusables/gated-features/auto-merge.md +++ b/translations/zh-CN/data/reusables/gated-features/auto-merge.md @@ -1 +1 @@ -Auto-merge for pull requests 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" %}{% data reusables.gated-features.more-info %}{% endif %} \ No newline at end of file +Auto-merge for pull requests 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 %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/zh-CN/data/reusables/gated-features/code-scanning.md b/translations/zh-CN/data/reusables/gated-features/code-scanning.md index 2bfe160a80..35598cce54 100644 --- a/translations/zh-CN/data/reusables/gated-features/code-scanning.md +++ b/translations/zh-CN/data/reusables/gated-features/code-scanning.md @@ -1 +1,4 @@ -{% if currentVersion == "free-pro-team@latest" %}{% 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 %} +{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled. +{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository. +{%- else %} +{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} 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 1f787e8a8a..2af4bce7f0 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 @@ -1,8 +1,8 @@ -| 虚拟环境 | YAML 工作流程标签 | -| -------------------- | --------------------------------- | -| Windows Server 2019 | `windows-latest` 或 `windows-2019` | -| Ubuntu 20.04 | `ubuntu-20.04` | -| Ubuntu 18.04 | `ubuntu-latest` 或 `ubuntu-18.04` | -| Ubuntu 16.04 | `ubuntu-16.04` | -| macOS Big Sur 11.0 | `macos-11.0` | -| macOS Catalina 10.15 | `macos-latest` 或 `macos-10.15` | +| 虚拟环境 | YAML 工作流程标签 | +| -------------------- | -------------------------------------------- | +| Windows Server 2019 | `windows-latest` 或 `windows-2019` | +| Ubuntu 20.04 | `ubuntu-latest` (see note) or `ubuntu-20.04` | +| Ubuntu 18.04 | `ubuntu-latest` (see note) or `ubuntu-18.04` | +| Ubuntu 16.04 | `ubuntu-16.04` | +| macOS Big Sur 11.0 | `macos-11.0` | +| macOS Catalina 10.15 | `macos-latest` 或 `macos-10.15` | diff --git a/translations/zh-CN/data/reusables/github-actions/ubuntu-runner-preview.md b/translations/zh-CN/data/reusables/github-actions/ubuntu-runner-preview.md index 30fb19a529..6eb91edc13 100644 --- a/translations/zh-CN/data/reusables/github-actions/ubuntu-runner-preview.md +++ b/translations/zh-CN/data/reusables/github-actions/ubuntu-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**注：**Ubuntu 20.04 虚拟环境目前仅作为预览提供。 `ubuntu-latest` YAML 工作流程标签仍使用 Ubuntu 18.04 虚拟环境。 +**Note:** The `ubuntu-latest` label is currently being migrated from the Ubuntu 18.04 virtual environment to Ubuntu 20.04. Specifying the `ubuntu-latest` label during the migration might use either virtual environment. To explicitly use Ubuntu 20.04 or Ubuntu 18.04, specify `ubuntu-20.04` or `ubuntu-18.04`. When the migration is complete, `ubuntu-latest` will use the Ubuntu 20.04 virtual environment. For more information about the migration, see "[Ubuntu-latest workflows will use Ubuntu-20.04](https://github.com/actions/virtual-environments/issues/1816)." {% endnote %} diff --git a/translations/zh-CN/data/reusables/organizations/organizations_include.md b/translations/zh-CN/data/reusables/organizations/organizations_include.md index 2ca103b281..b8a8d63347 100644 --- a/translations/zh-CN/data/reusables/organizations/organizations_include.md +++ b/translations/zh-CN/data/reusables/organizations/organizations_include.md @@ -6,3 +6,4 @@ - [反映公司或组结构的嵌套团队](/articles/about-teams)，级联了访问权限和提及{% if currentVersion != "github-ae@latest" %} - 组织所有者能够查看成员的[双重身份验证 (2FA) 状态](/articles/about-two-factor-authentication) - 用于[要求所有组织成员使用双重身份验证](/articles/requiring-two-factor-authentication-in-your-organization)的选项{% endif %} +{% if currentVersion == "free-pro-team@latest" %}- The option to purchase a license for {% data variables.product.prodname_GH_advanced_security %} and use the features on private repositories. {% data reusables.advanced-security.more-info-ghas %}{% endif %} diff --git a/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md b/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md index 4b6a5f5435..f93dafb946 100644 --- a/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md +++ b/translations/zh-CN/data/reusables/pages/new-or-existing-repo.md @@ -1,3 +1,5 @@ 如果站点是一个独立的项目，您可以创建新仓库来存储站点源代码。 如果您的站点与现有的项目关联，您可以添加站点的源代码添加{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}到该项目仓库的默认分支或其他分支上的 `/docs` 文件夹中。{% else %}到 `gh-pages` 分支或该项目仓库 `master` 分支上的 `docs` 文件夹中。{% endif %} 例如，如果您创建站点来发布已经在 {% data variables.product.product_name %} 中的项目文档， 您可能想要将站点的源代码存储在与项目相同的仓库中。 +{% if currentVersion == "free-pro-team@latest" %}If the account that owns the repository uses {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_free_team %}, the repository must be public.{% endif %} + 如果要在现有仓库中创建站点，请跳至“[创建站点](#creating-your-site)”一节。 diff --git a/translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md index 93c18a9fe8..fb7617bcb7 100644 --- a/translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md +++ b/translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -2,6 +2,6 @@ 要变基并合并拉取请求，必须在仓库中拥有[写入权限](/articles/repository-permission-levels-for-an-organization/)，并且仓库必须[允许变基合并](/articles/configuring-commit-rebasing-for-pull-requests/)。 -{% data variables.product.product_name %} 上的变基和合并行为与 `git rebase` 略有偏差。 {% data variables.product.prodname_dotcom %} 上的变基和合并始终会更新提交者信息并创建新的提交 SHA，而 {% data variables.product.prodname_dotcom %} 外部的 `git rebase` 在提交原型上发生变基时不改变提交者信息。 For more information about `git rebase`, see [the official Git documentation](https://git-scm.com/docs/git-rebase). +{% data variables.product.product_name %} 上的变基和合并行为与 `git rebase` 略有偏差。 {% data variables.product.prodname_dotcom %} 上的变基和合并始终会更新提交者信息并创建新的提交 SHA，而 {% data variables.product.prodname_dotcom %} 外部的 `git rebase` 在提交原型上发生变基时不改变提交者信息。 有关 `git rebase` 的更多信息，请参阅[官方 Git 文档](https://git-scm.com/docs/git-rebase)。 有关 `git rebase` 的可视表示，请参阅 _Pro Git_ 一书中的[“Git 分支 - 变基”一章](https://git-scm.com/book/en/Git-Branching-Rebasing)。 diff --git a/translations/zh-CN/data/reusables/pull_requests/you-can-auto-merge.md b/translations/zh-CN/data/reusables/pull_requests/you-can-auto-merge.md index a5bcbffeae..8cc765707c 100644 --- a/translations/zh-CN/data/reusables/pull_requests/you-can-auto-merge.md +++ b/translations/zh-CN/data/reusables/pull_requests/you-can-auto-merge.md @@ -1,3 +1,3 @@ -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} You can configure a pull request to merge automatically when all merge requirements are met. 更多信息请参阅“[自动合并拉取请求](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)”。 -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md index 293058d64a..806d0ca62b 100644 --- a/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md @@ -1,3 +1,3 @@ -| 键 | 类型 | 描述 | -| -------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. 如果操作为 `closed`，并且 `merged` 键为 `false`，则拉取请求随未合并的提交而关闭。 如果操作为 `closed`，并且 `merged` 键为 `true`，则拉取请求被合并。 | +| 键 | 类型 | 描述 | +| -------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `字符串` | 执行的操作内容. 可以是以下之一：`opened`、`edited`、`closed`、`assigned`、`unassigned`、`review_requested`、`review_request_removed`、`ready_for_review`、`converted_to_draft`、`labeled`、`unlabeled`、`synchronize`、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}`auto_merge_enabled`、`auto_merge_disabled`、{% endif %} `locked`、`unlocked` 或 `reopened`。 如果操作为 `closed`，并且 `merged` 键为 `false`，则拉取请求随未合并的提交而关闭。 如果操作为 `closed`，并且 `merged` 键为 `true`，则拉取请求被合并。 | diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml index 6570d67a67..763fb0c90e 100644 --- a/translations/zh-CN/data/ui.yml +++ b/translations/zh-CN/data/ui.yml @@ -143,7 +143,7 @@ product_sublanding: no_result: 抱歉，没有与过滤条件匹配的指南。 filters: type: 类型 - topic: Topic + topic: 主题 all: 所有 guide_types: overview: 概览 diff --git a/translations/zh-CN/data/variables/action_code_examples.yml b/translations/zh-CN/data/variables/action_code_examples.yml index 11401c6912..88a621a00f 100644 --- a/translations/zh-CN/data/variables/action_code_examples.yml +++ b/translations/zh-CN/data/variables/action_code_examples.yml @@ -12,7 +12,7 @@ languages: JavaScript href: lannonbr/issue-label-manager-action tags: - - issues + - 议题 - labels - title: 声明同步 GitHub 标签 @@ -20,11 +20,11 @@ languages: 'Go, Dockerfile' href: micnncim/action-label-syncer tags: - - issues + - 议题 - labels - title: 向 GitHub 添加版本 - description: 在操作中发布 Github 版本 + description: Publish GitHub releases in an action languages: 'Dockerfile, Shell' href: elgohr/Github-Release-Action tags: @@ -32,7 +32,7 @@ - 发布 - title: 向 Dockerhub 发布 Docker 映像 - description: 用于生成和发布 Docker 映像的 Github 操作 + description: A GitHub Action used to build and publish Docker images languages: 'Dockerfile, Shell' href: elgohr/Publish-Docker-Github-Action tags: @@ -45,7 +45,7 @@ languages: 'JavaScript, Python' href: peter-evans/create-issue-from-file tags: - - issues + - 议题 - title: 使用资产发布 GitHub 版本 description: 用于创建 GitHub 版本的 GitHub 操作 @@ -62,7 +62,7 @@ tags: - projects - automation - - issues + - 议题 - 拉取请求 - title: 使用 Web 界面在本地运行 GitHub Actions @@ -123,16 +123,16 @@ - 发布 - title: 自动标记您的拉取请求（使用提交的文件） - description: 自动标记拉取请求（使用提交的文件）的 Github 操作 + description: GitHub action to label your pull requests auto-magically (using committed files) languages: 'TypeScript, Dockerfile, JavaScript' href: Decathlon/pull-request-labeler-action tags: - projects - - issues + - 议题 - labels - title: 根据作者团队名称向拉取请求添加标签 - description: 根据作者名称标记拉取请求的 Github 操作 + description: GitHub action to label your pull requests based on the author name languages: 'TypeScript, JavaScript' href: JulienKode/team-labeler-action tags: @@ -163,7 +163,7 @@ - 工作流程 - tools - labels - - issues + - 议题 - title: 回滚 GitHub 版本 description: 回滚或删除版本的 GitHub 操作 @@ -178,7 +178,7 @@ languages: 'JavaScript' href: dessant/lock-threads tags: - - issues + - 议题 - 拉取请求 - 工作流程 - @@ -234,7 +234,7 @@ href: robvanderleek/create-issue-branch tags: - probot - - issues + - 议题 - labels - title: 删除旧构件 diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml index bafe52a212..890c56d3a0 100644 --- a/translations/zh-CN/data/variables/product.yml +++ b/translations/zh-CN/data/variables/product.yml @@ -147,10 +147,10 @@ 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://docs.github.com/rest{% elsif enterpriseServerVersions contains currentVersion %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif currentVersion == "github-ae@latest" %}https://docs.github.com/github-ae@latest/rest{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% endif %} #Use this inside command-line code blocks #Enterprise OAuth paths that don't include "/graphql" or "/api/v3" oauth_host_code: >- @@ -159,10 +159,10 @@ device_authorization_url: >- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}[`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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% 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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/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 %} + {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/graphql{% endif %}